From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthew Hall <mhall@mhcomputing.net>
Subject: Re: clang build failing in v2.0.0 from poisoned symbols
Date: Thu, 18 Jun 2015 21:31:02 -0700
Message-ID: <20150619043102.GA25396@mhcomputing.net>
References: <20150619033746.GA24292@mhcomputing.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186])
 by dpdk.org (Postfix) with ESMTP id 181D7C67E
 for <dev@dpdk.org>; Fri, 19 Jun 2015 06:33:34 +0200 (CEST)
Content-Disposition: inline
In-Reply-To: <20150619033746.GA24292@mhcomputing.net>
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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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.