From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Peter Seiderer <ps.report@gmx.net>
Cc: Buildroot Mailing List <buildroot@buildroot.org>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH v2, 1/1] package/file: fix build with gcc 4.8
Date: Sat, 8 Jan 2022 19:38:00 +0100 [thread overview]
Message-ID: <20220108193800.5f91ac3b@windsurf> (raw)
In-Reply-To: <20220108183919.238c1885@gmx.net>
On Sat, 8 Jan 2022 18:39:19 +0100
Peter Seiderer <ps.report@gmx.net> wrote:
> 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)...
But why the solution we use for the target package doesn't work for the
host package?
Or perhaps we're no longer testing the target package with gcc 4.8 ?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-08 18:38 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
2022-01-08 18:38 ` Thomas Petazzoni [this message]
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=20220108193800.5f91ac3b@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=ps.report@gmx.net \
--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.