From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] toolchain: add 4.18.x choice for headers
Date: Thu, 06 Sep 2018 21:17:01 +0200 [thread overview]
Message-ID: <871sa68mhe.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180906100534.6fe06c24@windsurf> (Thomas Petazzoni's message of "Thu, 6 Sep 2018 10:05:34 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> Hello J?r?me,
> On Thu, 6 Sep 2018 09:42:16 +0200, Jerome Forissier wrote:
>> Signed-off-by: Jerome Forissier <jerome.forissier@linaro.org>
>> ---
>> toolchain/Config.in | 5 +++++
>> .../toolchain-external/toolchain-external-custom/Config.in.options | 4 ++++
>> 2 files changed, 9 insertions(+)
>>
>> FYI, this is needed in order to use the GCC 8.2.x recently published by
>> Arm [1] as an external toolchain.
>>
>> [1] https://developer.arm.com/open-source/gnu-toolchain/gnu-a/downloads
> Thanks for this patch. In fact, we already have this in our "next"
> branch:
> https://git.buildroot.org/buildroot/commit/toolchain?h=next&id=7f62d8122bc42b84608cad34fb005b4870c143d5
> But we could indeed have it in the master branch, so that the most
> recent toolchains can be used even with our upcoming 2018.08 release.
I've now cherry picked this commit for master.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-09-06 19:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180906074216.32688-1-jerome.forissier@linaro.org>
2018-09-06 8:05 ` [Buildroot] [PATCH 1/1] toolchain: add 4.18.x choice for headers Thomas Petazzoni
2018-09-06 8:26 ` Jerome Forissier
2018-09-06 19:17 ` 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=871sa68mhe.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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