From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id 181D7C67E for ; Fri, 19 Jun 2015 06:33:34 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 38C1C80C502; Thu, 18 Jun 2015 21:31:02 -0700 (PDT) Date: Thu, 18 Jun 2015 21:31:02 -0700 From: Matthew Hall To: dev@dpdk.org Message-ID: <20150619043102.GA25396@mhcomputing.net> References: <20150619033746.GA24292@mhcomputing.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150619033746.GA24292@mhcomputing.net> User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] clang build failing in v2.0.0 from poisoned symbols X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jun 2015 04:33:34 -0000 On Thu, Jun 18, 2015 at 08:37:46PM -0700, Matthew Hall wrote: > dpdk/lib/librte_mbuf/rte_mbuf.h:68:20: error: poisoning existing macro [-Werror] Hi all, I finally figured out what happened. My older DPDK build configuration file had defined the poisoned macros to try to enable the features they used to cover, which had been obsoleted and/or replaced. I am happy to be able to report that my app compiled with no changes once I rebased my locally tweaked DPDK onto the v2.0.0 tag... very impressive work... we might not be binary compatible but we definitely seem to be source compatible for my app at least. Considering most people use the static library this is not a bad state to start with I'd say. Matthew.