From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [git commit] support/config-fragments/autobuild/bootlin-armv7m-uclibc.config: specify configuration more precisely
Date: Thu, 22 Sep 2022 14:33:33 +0200 [thread overview]
Message-ID: <87edw3d1wi.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220917124845.2A95484258@busybox.osuosl.org> (Thomas Petazzoni's message of "Sat, 17 Sep 2022 14:45:47 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> commit: https://git.buildroot.net/buildroot/commit/?id=43fc826d82acc089991d561ebca37feaf1aa421d
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> Due to a bug in the CodeSourcery ARM toolchain packaging, this
> toolchain currently appears as available even for noMMU
> configurations, which is obviously wrong. Due to this, the
> bootlin-armv7m-uclibc.config fragment ends up using the CodeSourcery
> ARM toolchain, which is obviously wrong for an ARM noMMU
> configuration, causing a build failure when matching the toolchain
> capabilities with the configuration.
> Even though we will separately fix the CodeSourcery ARM toolchain
> packaging, it makes sense to ensure that the
> bootlin-armv7m-uclibc.config fragment explicitly selects the Bootlin
> toolchain.
> Reported-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Committed to 2022.02.x, 2022.05.x and 2022.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-09-22 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 12:45 [Buildroot] [git commit] support/config-fragments/autobuild/bootlin-armv7m-uclibc.config: specify configuration more precisely Thomas Petazzoni
2022-09-22 12:33 ` 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=87edw3d1wi.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--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.