From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bruce.richardson@intel.com>
Received: from mga01.intel.com (mga01.intel.com [192.55.52.88])
 by dpdk.org (Postfix) with ESMTP id 85AADC73A
 for <dev@dpdk.org>; Fri, 19 Jun 2015 12:15:35 +0200 (CEST)
Received: from fmsmga001.fm.intel.com ([10.253.24.23])
 by fmsmga101.fm.intel.com with ESMTP; 19 Jun 2015 03:15:34 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.13,643,1427785200"; d="scan'208";a="730560025"
Received: from bricha3-mobl3.ger.corp.intel.com ([10.243.20.21])
 by fmsmga001.fm.intel.com with SMTP; 19 Jun 2015 03:15:32 -0700
Received: by  (sSMTP sendmail emulation); Fri, 19 Jun 2015 11:15:31 +0025
Date: Fri, 19 Jun 2015 11:15:31 +0100
From: Bruce Richardson <bruce.richardson@intel.com>
To: Matthew Hall <mhall@mhcomputing.net>
Message-ID: <20150619101531.GC6880@bricha3-MOBL3>
References: <20150619033746.GA24292@mhcomputing.net>
 <20150619043102.GA25396@mhcomputing.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150619043102.GA25396@mhcomputing.net>
Organization: Intel Shannon Ltd.
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: dev@dpdk.org
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 <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jun 2015 10:15:36 -0000

On Thu, Jun 18, 2015 at 09:31:02PM -0700, Matthew Hall wrote:
> 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.

Thank you. It's finally nice to get some good news about compatibility! :-)