From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Bernd Kuhls <bernd@kuhls.net>,
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>,
Pedro Aguilar <paguilar@paguilar.org>
Subject: Re: [Buildroot] [PATCH 1/1] toolchain: drop codesourcery arm/aarch64 toolchains
Date: Thu, 14 Mar 2024 19:48:43 +0100 [thread overview]
Message-ID: <87wmq4myyc.fsf@48ers.dk> (raw)
In-Reply-To: <20240309164946.166802-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sat, 9 Mar 2024 17:49:46 +0100")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> codesourcery arm/aarch64 toolchains are old (2014) and use glibc
> 2.18/2.20 which are not compatible with 64-bit time_t raising the
> following build failure with libcgroup since commit
> 1c2dbcdcf0bb589d325c379246acaa39bb07b7be:
> In file included from ./libcgroup-internal.h:25:0,
> from parse.y:21:
> /home/buildroot/autobuild/run/instance-3/output-1/host/arm-buildroot-linux-gnueabi/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/e28f955f2b360f6e7bb231a5a3800cfbd17a23d7
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/guile/guile.mk | 5 -
> package/mesa3d/mesa3d.mk | 6 --
> package/tpm2-totp/Config.in | 2 -
> .../autobuild/sourcery-arm-armv4t.config | 4 -
> .../autobuild/sourcery-arm-thumb2.config | 7 --
> .../autobuild/sourcery-arm.config | 3 -
> .../autobuild/toolchain-configs.csv | 5 -
> .../testing/tests/toolchain/test_external.py | 97 -------------------
> toolchain/Config.in | 1 -
I get a conflict here, so this was presumably not generated against
master?
Committed after fixing that up and adding Config.in.legacy entries,
thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-03-14 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 16:49 [Buildroot] [PATCH 1/1] toolchain: drop codesourcery arm/aarch64 toolchains Fabrice Fontaine
2024-03-14 18:48 ` Peter Korsgaard [this message]
2024-03-15 19:40 ` Arnout Vandecappelle via buildroot
2024-03-16 15:07 ` Peter Korsgaard
2024-03-21 20:44 ` 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=87wmq4myyc.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=paguilar@paguilar.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox