From: Peter Seiderer <ps.report@gmx.net>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v2, 1/1] package/file: fix build with gcc 4.8
Date: Sat, 8 Jan 2022 18:39:19 +0100 [thread overview]
Message-ID: <20220108183919.238c1885@gmx.net> (raw)
In-Reply-To: <CAPi7W82_k_toe+-1DdZv8wr2ArKjeZfb9qdarm5oewv52vsh4g@mail.gmail.com>
Hello Fabrice, *,
On Sat, 8 Jan 2022 17:13:47 +0100, Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Hi,
>
> Le sam. 8 janv. 2022 à 11:51, Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> a écrit :
> >
> > On Tue, 4 Jan 2022 21:54:55 +0100
> > Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> >
> > > Fix the following build failure raised since bump to version 5.41 in
> > > commit d38b72bcd75392a88b5100839ac410859d0a6a79:
> > >
> > > readelf.c: In function 'do_auxv_note':
> > > readelf.c:1046:2: error: 'for' loop initial declarations are only allowed in C99 mode
> > > for (size_t off = 0; off + elsize <= descsz; off += elsize) {
> > > ^
> > >
> > > Fixes:
> > > - http://autobuild.buildroot.org/results/31cbc313fceb84c0cbb1969fca5ac44244871dbc
> > >
> > > Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> >
> > I am afraid it seems like this didn't fix the problem, see:
> >
> > http://autobuild.buildroot.net/results/957/9573e8b01d8f21cd89a67475daabdeef533d31d7/build-end.log
> >
> > ac_cv_prog_cc_c99='-std=gnu99' is properly passed to the configure
> > script, but it still fails.
> Indeed, I suggest to revert this commit and apply the version 1 of
> this patch instead of trying to understand what is "broken" in the
> configure script.
The difference seems to be:
$ diff -ru file-5.38/configure.ac file-5.41/configure.ac
[...]
@@ -88,7 +88,7 @@
AC_SUBST(WARNINGS)
dnl Checks for programs.
-AC_PROG_CC_STDC
+AC_PROG_CC
AC_USE_SYSTEM_EXTENSIONS
AM_PROG_CC_C_O
AC_C_BIGENDIAN
[...]
According to [1] AC_PROG_CC checks/enables c89 and AC_PROG_CC_STDC checks/enabls C99 (or
use AC_PROG_CC_C99 to be more explicit)..., note that with AC_PROG_CC the ac_cv_prog_cc_c99
feature is gone (still used for target/host in package/file/file.mk)...
Regards,
Peter
[1] https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/C-Compiler.html
> >
> > Thomas
> > --
> > Thomas Petazzoni, co-owner and CEO, Bootlin
> > Embedded Linux and Kernel engineering and training
> > https://bootlin.com
> Best Regards,
>
> Fabrice
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-08 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 20:54 [Buildroot] [PATCH v2,1/1] package/file: fix build with gcc 4.8 Fabrice Fontaine
2022-01-07 18:08 ` [Buildroot] [PATCH v2, 1/1] " Thomas Petazzoni
2022-01-08 10:51 ` Thomas Petazzoni
2022-01-08 16:13 ` Fabrice Fontaine
2022-01-08 17:39 ` Peter Seiderer [this message]
2022-01-08 18:38 ` Thomas Petazzoni
2022-01-08 18:46 ` Fabrice Fontaine
2022-01-08 18:50 ` Arnout Vandecappelle
2022-01-08 20:41 ` Fabrice Fontaine
2022-01-08 22:04 ` Yann E. MORIN
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=20220108183919.238c1885@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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.