From: Bernhard Walle <bernhard@bwalle.de>
To: ptxdist@pengutronix.de
Cc: Bernhard Walle <bernhard@bwalle.de>
Subject: [ptxdist] [PATCH 1/3] host-ncurses: Fix build with gcc 5.1
Date: Sat, 2 May 2015 14:42:39 +0200 [thread overview]
Message-ID: <1430570561-19891-2-git-send-email-bernhard@bwalle.de> (raw)
In-Reply-To: <1430570561-19891-1-git-send-email-bernhard@bwalle.de>
The build of host-ncurses fails with following error:
| In file included from ../ncurses/curses.priv.h:283:0,
| from ../ncurses/lib_gen.c:19:
| _16905.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)
The problem is that the preprocessor emits additional line statements which
ncurses isn't prepared for. The problem is described in the gcc 5 porting
guide at https://gcc.gnu.org/gcc-5/porting_to.html. Adding the described
-P option to gcc invocations fixes that issue.
Signed-off-by: Bernhard Walle <bernhard@bwalle.de>
---
rules/host-ncurses.make | 3 +++
1 file changed, 3 insertions(+)
diff --git a/rules/host-ncurses.make b/rules/host-ncurses.make
index 2218b7c..67dbf5b 100644
--- a/rules/host-ncurses.make
+++ b/rules/host-ncurses.make
@@ -21,6 +21,9 @@ HOST_PACKAGES-$(PTXCONF_HOST_NCURSES) += host-ncurses
# autoconf
#
HOST_NCURSES_CONF_TOOL := autoconf
+HOST_NCURSES_CONF_ENV := \
+ $(HOST_ENV) \
+ CPPFLAGS="-P"
HOST_NCURSES_CONF_OPT = \
$(HOST_AUTOCONF) \
$(NCURSES_AUTOCONF_SHARED)
--
2.3.7
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-05-02 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 12:42 [ptxdist] gcc 5.1 fixes Bernhard Walle
2015-05-02 12:42 ` Bernhard Walle [this message]
2015-05-02 12:42 ` [ptxdist] [PATCH 2/3] host-localedef: Fix build with gcc 5.1 Bernhard Walle
2015-05-02 12:42 ` [ptxdist] [PATCH 3/3] host-mtd-utils: " Bernhard Walle
2015-05-04 8:49 ` [ptxdist] gcc 5.1 fixes Michael Olbrich
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=1430570561-19891-2-git-send-email-bernhard@bwalle.de \
--to=bernhard@bwalle.de \
--cc=ptxdist@pengutronix.de \
/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