From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-09-11
Date: Mon, 12 Sep 2016 23:54:30 +0200 [thread overview]
Message-ID: <20160912215430.GC15314@free.fr> (raw)
In-Reply-To: <20160912234452.38288933@free-electrons.com>
Thomas, All,
On 2016-09-12 23:44 +0200, Thomas Petazzoni spake thusly:
> On Mon, 12 Sep 2016 14:39:43 -0700, Alistair Francis wrote:
> > > aarch64 | xen-4.7.0 | NOK | http://autobuild.buildroot.net/results/9e733b8afb51add44fcf675fb25c05fe52773de7
> > > arm | xen-4.7.0 | NOK | http://autobuild.buildroot.net/results/fc39051eb0c466493a69bd9a320e6046a66db51e
> > > arm | xen-4.7.0 | NOK | http://autobuild.buildroot.net/results/65096ed770f89da2c928f504d84fc811619037d5
> > > arm | xen-4.7.0 | NOK | http://autobuild.buildroot.net/results/051d916bb12f1a0a0bfc5e2362e7a9b1488717f1
> > > arm | xen-4.7.0 | NOK | http://autobuild.buildroot.net/results/bcd784b22c0335c04960e1a5601e1925134f5edf
> > > arm | xen-4.7.0 | NOK | http://autobuild.buildroot.net/results/563f086f127b2a59edbe2adcfd730378d1a5d5f0
> >
> > Xen 4.7 has started failing and it looks to be related to a lack of
> > gettext. I can't see any recent changes that should have broken this.
> >
> > Does anyone have any idea what has changed with gettext?
>
> I don't see anything gettext related in there. What I see is:
>
> /usr/bin/gcc -Wp,-MD,tools/kconfig/.zconf.tab.o.d -Wall -Werror -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -Wdeclaration-after-statement -DCURSES_LOC="<ncurses.h>" -DLOCALE -DKBUILD_NO_NLS -Itools/kconfig -c -o tools/kconfig/zconf.tab.o tools/kconfig/zconf.tab.c
> In file included from tools/kconfig/zconf.tab.c:2576:0:
> tools/kconfig/confdata.c: In function 'conf_set_all_new_symbols':
> tools/kconfig/confdata.c:1167:2: error: ISO C90 forbids mixed declarations and code [-Werror=declaration-after-statement]
> cc1: all warnings being treated as errors
>
> I.e, the built-in kconfig copy of the Xen sources doesn't build with
> the host compiler on this machine. All issues appear on gcc20, where
> the host compiler is gcc 4.7.
>
> I guess the easiest fix here is to remove -Werror from the compile
> command line. Can you look at how to do this inside the Xen source code?
There's also http://autobuild.buildroot.net/results/bcd/bcd784b22c0335c04960e1a5601e1925134f5edf
which has seemingly gettext-related issues:
/usr/bin/gcc -Wp,-MD,tools/kconfig/.zconf.tab.o.d -Wall -Werror -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -Wdeclaration-after-statement -DCURSES_LOC="<ncurses.h>" -DNCURSES_WIDECHAR=1 -DLOCALE -DKBUILD_NO_NLS -Itools/kconfig -c -o tools/kconfig/zconf.tab.o tools/kconfig/zconf.tab.c
tools/kconfig/conf.c: In function 'check_stdin':
tools/kconfig/conf.c:77:3: error: format not a string literal and no format arguments [-Werror=format-security]
printf(_("aborted!\n\n"));
^
But again this is not because of gettext, but because of -Werror=format-security
which warns when the format string is not a constant.
But again, removing -Werror would do the trick.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-09-12 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-09-11 Thomas Petazzoni
2016-09-12 21:39 ` Alistair Francis
2016-09-12 21:44 ` Thomas Petazzoni
2016-09-12 21:54 ` Yann E. MORIN [this message]
2016-09-12 22:54 ` Alistair Francis
2016-09-13 16:23 ` Yann E. MORIN
2016-09-13 20:38 ` Alistair Francis
2016-09-13 23:15 ` Arnout Vandecappelle
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=20160912215430.GC15314@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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