From: Matthew Hall <mhall@mhcomputing.net>
To: dev@dpdk.org
Subject: Re: clang build failing in v2.0.0 from poisoned symbols
Date: Thu, 18 Jun 2015 21:31:02 -0700 [thread overview]
Message-ID: <20150619043102.GA25396@mhcomputing.net> (raw)
In-Reply-To: <20150619033746.GA24292@mhcomputing.net>
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.
next prev parent reply other threads:[~2015-06-19 4:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 3:37 clang build failing in v2.0.0 from poisoned symbols Matthew Hall
2015-06-19 4:31 ` Matthew Hall [this message]
2015-06-19 10:15 ` Bruce Richardson
2015-06-21 2:37 ` DPDK v2.0.0 has different rte_eal_pci_probe() behavior Matthew Hall
[not found] ` <CAO1kT8_C2QJUrNk-fqOQd=WmOkpvNw5jCvxEhfPdHwyCwBuyKA@mail.gmail.com>
2015-06-22 0:32 ` Matthew Hall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150619043102.GA25396@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).