[Buildroot] [PATCH v2 1/1] toolchain: update AArch32/AArch64 toolchains to 8-2-2019.01
Arnout Vandecappelle
arnout at mind.be
Mon Feb 4 12:42:07 UTC 2019
On 04/02/2019 11:08, Peter Korsgaard wrote:
>>>>>> "Arnout" == Arnout Vandecappelle <arnout at mind.be> writes:
>
> > On 29/01/2019 12:27, Arnout Vandecappelle wrote:
> >>>> On 28/01/2019 18:05, Joakim Bech wrote:
> >>>> [snip]
> >>>>> +config BR2_KERNEL_HEADERS_5_00
> >>>>> + bool "Linux 5.00.x kernel headers"
> >>>>> + select BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_00
> >>>> Adding support for the 5.0 headers should be a separate patch. See commit
> >>>> 649883d2c9957b7a7fcf81c4475f848ad8865ca1 for an example how it was done for 4.20.
> >>>>
> >>> So after looking a bit more into the git log of how patches where
> >>> created in the past it looks like I should create 4 patches, "pseudo git
> >>> log -4".
> >>> - toolchain-external: update Arm ARM 8.2-2019.01
> >>> - toolchain-external: update Arm AArch64-BE toolchain 8.2-2019.01
> >>> - toolchain-external: update Arm AArch64 toolchain 8.2-2019.01
> >>> - toolchain: add necessary options to support 5.0 kernel headers
> >> Indeed, that's the way to go.
>
> > Hold on a moment, I'm having second thoughts on this... This toolchain is using
> > 5.0-rcX kernel headers. I'm not so sure that we will want that in our 2019.02
> > LTS release... So I expect that this patch will not get included in the 2919.02
> > cut-off, and will end up being superseded by the Arm 2019.03 release...
>
> > Peter?
>
> Yes, using a RC doesn't sound very nice for the LTS.
>
> > That said, the part that adds support for 5.0 kernel headers is certainly
> > something we'd like to have in the 2019.02 LTS.
>
> Why? 5.0 is not released yet, and will not become a LTS release.
It is likely that people will use a 5.0 kernel during the LTS cycle, and that
they will use HEADERS_AS_KERNEL.
Actually, we should have have a _REALLY_NEW option for custom headers, just
like we have _REALLY_OLD.
Regards,
Arnout
More information about the buildroot
mailing list