From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: "Karoly Kasza" <kaszak@gmail.com>,
"Hervé Codina" <herve.codina@bootlin.com>,
"Ezequiel Garcia" <ezequiel@vanguardiasur.com.ar>,
"Raphael Pavlidis" <raphael.pavlidis@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/linux-pam: needs gcc >= 4.9
Date: Sat, 30 Sep 2023 12:20:31 +0200 [thread overview]
Message-ID: <87edigaro0.fsf@48ers.dk> (raw)
In-Reply-To: <20230916135435.113400-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sat, 16 Sep 2023 15:54:35 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> linux-pam raises the following build failure with gcc 4.8 since bump to
> version 1.5.3 in commit f8147e27cdac8f998ec6644a09ce4e8d62b6433c and
> https://github.com/linux-pam/linux-pam/commit/8f9816b57e3a475fc2d2cbb106c188b778098f85:
> pam_access.c: In function 'pam_sm_authenticate':
> pam_access.c:1084:13: error: 'for' loop initial declarations are only allowed in C99 mode
> for (int i = 0; filename_list[i] != NULL; i++) {
> ^
> Those build failures could be fixed by adding -std=c99 but then the
> build will fails because stdadtomic.h is mandatory since
> https://github.com/linux-pam/linux-pam/commit/a35e092e24ee7632346a0e1b4a203c04d4cd2c62
> Fixes:
> - http://autobuild.buildroot.org/results/9b2ba987d2c873f4a7caea72707acb655279d16b
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-30 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 13:54 [Buildroot] [PATCH 1/1] package/linux-pam: needs gcc >= 4.9 Fabrice Fontaine
2023-09-30 10:20 ` Peter Korsgaard [this message]
2023-10-12 16:47 ` Peter Korsgaard
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=87edigaro0.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=fontaine.fabrice@gmail.com \
--cc=herve.codina@bootlin.com \
--cc=kaszak@gmail.com \
--cc=raphael.pavlidis@gmail.com \
/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.