From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: what feature fixed the gcc-5 preprocessor build error from a few months back?
Date: Mon, 7 Dec 2015 04:44:52 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.20.1512070440340.13574@localhost> (raw)
once upon a time, i asked a question about the origin of this OE
build error using gcc-5 to build ncurses-native:
> In file included from
/home/rpjday/oe/builds/oe/qemux86/tmp-glibc/work/x86_64-linux/ncurses-native/5.9-r15.1/ncurses-5.9/ncurses/curses.priv.h:283:0,
> from ../ncurses/lib_gen.c:19:
> _20141.c:835:15: error: expected ')' before 'int'
> ../include/curses.h:1594:56: note: in definition of macro
'mouse_trafo'
> #define mouse_trafo(y,x,to_screen)
wmouse_trafo(stdscr,y,x,to_screen)
it didn't take long to be pointed to an explanation on the fedora
mailing list:
http://lists.openembedded.org/pipermail/openembedded-core/2015-February/101820.html
" these packages failed to build because of the changes in the preprocessor;
gcc started to generate line directives to better detect whether a macro
tokens come from a system header - see http://gcc.gnu.org/PR60723
The fix is to use the -P option if the code isn't prepared to deal with
such directives.
so i just added to my local.conf:
CPPFLAGS_append_pn-ncurses-native = " -P"
that issue was apparently fixed and i haven't needed to do that for
a while. however, i'm now using someone's custom version of OE-core
and that very error is back, so what was it that was tweaked to deal
with it? thanks.
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-12-07 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 9:44 Robert P. J. Day [this message]
2015-12-07 10:17 ` what feature fixed the gcc-5 preprocessor build error from a few months back? Andreas Oberritter
2015-12-07 12:41 ` Robert P. J. Day
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.20.1512070440340.13574@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.