"--disable-werror" versus "--disable-Werror"?

"--disable-werror" versus "--disable-Werror"?

[Robert P. J. Day]

  apparently another gcc-5.0.0 issue(or maybe not), but my build of
core-image-minimal for qemux86 now fails thusly trying to build
elfutils-native:

|
/home/rpjday/oe/builds/qemux86/tmp/work/x86_64-linux/elfutils-native/0.161-r0/elfutils-0.161/libebl/eblsectiontypename.c:111:28:
error: format '%x' expects argument of type 'unsigned int', but
argument 4 has type 'int' [-Werror=format=]
|         snprintf (buf, len, "SHT_LOOS+%x", section - SHT_LOOS);
|                             ^
|
/home/rpjday/oe/builds/qemux86/tmp/work/x86_64-linux/elfutils-native/0.161-r0/elfutils-0.161/libebl/eblsectiontypename.c:111:28:
error: format '%x' expects argument of type 'unsigned int', but
argument 4 has type 'int' [-Werror=format=]
|
/home/rpjday/oe/builds/qemux86/tmp/work/x86_64-linux/elfutils-native/0.161-r0/elfutils-0.161/libebl/eblsectiontypename.c:114:28:
error: format '%x' expects argument of type 'unsigned int', but
argument 4 has type 'int' [-Werror=format=]
|         snprintf (buf, len, "SHT_LOPROC+%x", section - SHT_LOPROC);
|                             ^
|
/home/rpjday/oe/builds/qemux86/tmp/work/x86_64-linux/elfutils-native/0.161-r0/elfutils-0.161/libebl/eblsectiontypename.c:114:28:
error: format '%x' expects argument of type 'unsigned int', but
argument 4 has type 'int' [-Werror=format=]
| cc1: all warnings being treated as errors

  since all warnings are being treated as errors, i did a quick check
to see how to disable that option on a per-recipe basis and *thought*
i could just add the following line to local.conf:

EXTRA_OECONF_pn-elfutils-native = "--disable-Werror"

but that didn't do it.  but there's more.

  i did a "grep" just to see how other recipes were doing it, and i
saw a mixture of "--disable-werror" versus "--disable-Werror", and
this web page which suggests that only one of those forms is correct:

http://patchwork.openembedded.org/patch/23361/

but feel free to search for yourself to see.

  in any event, what *is* the proper local.conf fix to disable this
option on a per-recipe basis?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: "--disable-werror" versus "--disable-Werror"?

[Richard Purdie]

On Tue, 2015-02-17 at 06:21 -0500, Robert P. J. Day wrote:
>   i did a "grep" just to see how other recipes were doing it, and i
> saw a mixture of "--disable-werror" versus "--disable-Werror", and
> this web page which suggests that only one of those forms is correct:
> 
> http://patchwork.openembedded.org/patch/23361/
> 
> but feel free to search for yourself to see.
> 
>   in any event, what *is* the proper local.conf fix to disable this
> option on a per-recipe basis?

It depends on the recipe in question and how its configuration is
enabling warnings as errors in the first place. There is no defined
standard mechanism for that afaik.

Cheers,

Richard