From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Julien Olivain <ju.o@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org, Romain Naour <romain.naour@gmail.com>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Subject: Re: [Buildroot] [PATCH 1/1] toolchain: drop codescape mips toolchains
Date: Fri, 22 Mar 2024 20:53:41 +0100 [thread overview]
Message-ID: <87il1e2gca.fsf@48ers.dk> (raw)
In-Reply-To: <20240317125133.362751-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sun, 17 Mar 2024 13:51:32 +0100")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> Codescape mips toolchains are old (2018) and use glibc 2.20 which is not
> compatible with 64-bit time_t raising the following build failure with
> libselinux since commit 1c2dbcdcf0bb589d325c379246acaa39bb07b7be:
> In file included from selinux_restorecon.c:17:0:
> /home/buildroot/autobuild/instance-1/output-1/host/mipsel-buildroot-linux-gnu/sysroot/usr/include/fts.h:41:3: error: #error "<fts.h> cannot be used with -D_FILE_OFFSET_BITS==64"
> # error "<fts.h> cannot be used with -D_FILE_OFFSET_BITS==64"
> ^~~~~
> Fixes: 1c2dbcdcf0bb589d325c379246acaa39bb07b7be
> - http://autobuild.buildroot.org/results/a4d38af627a42a2c55d60129787c51353d5883bf
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2024.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-03-22 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 12:51 [Buildroot] [PATCH 1/1] toolchain: drop codescape mips toolchains Fabrice Fontaine
2024-03-17 21:34 ` Arnout Vandecappelle via buildroot
2024-03-17 21:34 ` Arnout Vandecappelle via buildroot
2024-03-22 19:53 ` Peter Korsgaard [this message]
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=87il1e2gca.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=ju.o@free.fr \
--cc=romain.naour@gmail.com \
--cc=thomas.de_schampheleire@nokia.com \
--cc=thomas.petazzoni@bootlin.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.