From: Bruce Richardson <bruce.richardson@intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Andrew Rybchenko <arybchenko@solarflare.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/sfc: fix meson build warning with gcc
Date: Tue, 17 Apr 2018 09:59:33 +0100 [thread overview]
Message-ID: <20180417085933.GB77936@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20180416170930.56225-1-ferruh.yigit@intel.com>
On Mon, Apr 16, 2018 at 06:09:29PM +0100, Ferruh Yigit wrote:
> icc flag is causing build error with gcc, build error:
> cc1: warning: unrecognized gcc debugging option: i
> cc1: warning: unrecognized gcc debugging option: g
> cc1: warning: unrecognized gcc debugging option: -
> cc1: warning: unrecognized gcc debugging option: d
> cc1: warning: unrecognized gcc debugging option: i
> cc1: warning: unrecognized gcc debugging option: s
> cc1: warning: unrecognized gcc debugging option: b
> cc1: warning: unrecognized gcc debugging option: l
> cc1: warning: unrecognized gcc debugging option: e
> cc1: warning: unrecognized gcc debugging option:
> cc1: warning: unrecognized gcc debugging option: 3
> cc1: warning: unrecognized gcc debugging option: 6
> cc1: warning: unrecognized gcc debugging option: 5
> cc1: warning: unrecognized gcc debugging option: 6
> cc1: warning: unrecognized command line option
> ‘-Wno-address-of-packed-member’
>
> Removing icc flag completely since it is not supported right now.
>
> Fixes: f16d0b36f816 ("drivers/net: fix icc deprecated parameter warning")
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> Cc: Bruce Richardson <bruce.richardson@intel.com>
> ---
And just by way of further info, the underlying problem here is that gcc is
returning 0 i.e. not reporting error, when called normally with
-diag-disable flag. This prevents meson from detecting that the flag is
unsupported. :-(
/Bruce
prev parent reply other threads:[~2018-04-17 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 17:09 Ferruh Yigit
2018-04-16 17:31 ` Thomas Monjalon
2018-04-17 8:59 ` Bruce Richardson [this message]
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=20180417085933.GB77936@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
/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).