Skip to contentSkip to conversation

toolchain: add 4.18.x choice for headers

PATCH New Thomas Petazzoni 3 participants 3 messages Sep 6, 2018 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

PATCH 1/1 toolchain: add 4.18.x choice for headers

Hello J?r?me,

Quoted 10 lines · Jerome Forissier
---
 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.

Best regards,

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
#2 lore raw

PATCH 1/1 toolchain: add 4.18.x choice for headers

Quoted 12 lines · Thomas Petazzoni

Hello J?r?me,

Quoted 9 lines · Jerome Forissier
---
 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.

Quoted 6 lines
Quoted 1 line

[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

Ah, sorry for missing it. In fact I did not know about the existence of the "next" branch. Would you consider a patch to mention it in docs/manual/contribute.txt? I also got bitten by the fact that you need to be subscribed to the ML for patches to go through. Maybe another thing that {c,sh}ould be mentioned in the doc?

Quoted 3 lines

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.

Yes, that would help indeed.

Thanks,

Signature · 1 line
Jerome
Quoted 4 lines

Best regards,

Thomas

#3 lore raw

PATCH 1/1 toolchain: add 4.18.x choice for headers

In reply to Thomas Petazzoni
Quoted 15 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Thomas" == Thomas Petazzoni <[email protected]> writes:

Hello J?r?me,

Quoted 10 lines · Jerome Forissier

---
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

Quoted 7 lines

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.

Signature · 1 line
Bye, Peter Korsgaard