From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: "--disable-werror" versus "--disable-Werror"?
Date: Tue, 17 Feb 2015 06:21:28 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.11.1502170611270.21712@localhost> (raw)
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
========================================================================
next reply other threads:[~2015-02-17 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 11:21 Robert P. J. Day [this message]
2015-02-17 22:32 ` "--disable-werror" versus "--disable-Werror"? Richard Purdie
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=alpine.LFD.2.11.1502170611270.21712@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.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