dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: dev@dpdk.org
Subject: clang build failing in v2.0.0 from poisoned symbols
Date: Thu, 18 Jun 2015 20:37:46 -0700	[thread overview]
Message-ID: <20150619033746.GA24292@mhcomputing.net> (raw)

Hi all,

I am getting some odd behavior compiling the DPDK v2.0.0 tag with clang:

/* deprecated options */
#pragma GCC poison RTE_MBUF_SCATTER_GATHER
#pragma GCC poison RTE_MBUF_REFCNT

In file included from dpdk/lib/librte_mbuf/rte_mbuf.c:58:

dpdk/lib/librte_mbuf/rte_mbuf.h:68:20: error: poisoning existing macro [-Werror]

So I was reading about all of this and it was clear what poisoning is for, but 
it wasn't as clear what I should do about this error on the clang side. I 
tried searching the archive for "clang poison" but I didn't get much.

Any advice for this?

Thanks,
Matthew

             reply	other threads:[~2015-06-19  3:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19  3:37 Matthew Hall [this message]
2015-06-19  4:31 ` clang build failing in v2.0.0 from poisoned symbols Matthew Hall
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=20150619033746.GA24292@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).