From: "Wiles, Keith" <keith.wiles@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] e1000: unused variable warnings with clang
Date: Fri, 1 Jul 2016 17:35:09 +0000 [thread overview]
Message-ID: <A7FC2581-820F-4099-8284-2E0E100667F1@intel.com> (raw)
In-Reply-To: <0F5AACB9-1D9B-4F43-9E4C-E85735F5E427@intel.com>
On 7/1/16, 12:16 PM, "dev on behalf of Wiles, Keith" <dev-bounces@dpdk.org on behalf of keith.wiles@intel.com> wrote:
Well, after make sure I had CCACHE off and having the RTE_SDK variable set correctly, it does appear we have a problem building DPDK/e1000 directory with CLANG on my Ubuntu 16.04 updated as of today. If someone could please verify the if this is something in my system. Using T=x86_64-native-linuxapp-gcc does not have the same problem.
Using the following build line:
--------------
Sorry my bad, this is NOT a problem. Today is not my day ☹ woke up at 4:30am
next prev parent reply other threads:[~2016-07-01 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 14:50 Wiles, Keith
2016-07-01 17:16 ` Wiles, Keith
2016-07-01 17:35 ` Wiles, Keith [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-07-01 14:19 Wiles, Keith
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=A7FC2581-820F-4099-8284-2E0E100667F1@intel.com \
--to=keith.wiles@intel.com \
--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).