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.yi...@intel.com>
> ---
> Cc: Bruce Richardson <bruce.richard...@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
