Re: [Buildroot] [PATCH v1 0/8] support/kconfig: bump to linux-v6.9-rc5 version

[Peter Seiderer via buildroot <buildroot@buildroot.org>]

Hello Yann, Thomas,

On Mon, 6 May 2024 22:19:39 +0200, "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> Thomas, Peter, All,
>
> On 2024-05-06 21:04 +0200, Thomas Petazzoni via buildroot spake thusly:
> > On Mon,  6 May 2024 16:45:43 +0200
> > Peter Seiderer via buildroot <buildroot@buildroot.org> wrote:
> [--SNIP--]
> > > The kconfig version dump itself:
> > >   - support/kconfig: bump to linux-v6.9-rc5 version
> > So this commit without the next two leads to a broken situation,
> > correct? (Note: this is not a complaint, I agree with them being split).
>
> Except they should be reversed: the new commits can work with the
> kconfig we currently have, so it looks like it should be OK to do the
> required changes before doing the kconfig bump.

A solution for the two remaining patches working with the old/new kconfig would
be nice..., will test if it works for the escape problem...

Regards,
Peter

>
> > > And two 'real' changes due to kconfig language changes:
> > >   - support/kconfig: reference environment variables directly (remove 'option env=')
> > >   - package/openssl: move libopenssl/libressl source statemetns outside of the choice
> > But don't we have this situation of source statements inside a
> > choice..endchoice in other places?
>
> Toolchains, skeletons, init systems, jpeg library, linux extensions, and
> indeed openssl.
>
> > I remember Yann saying that this was
> > a problematic change for us in the upstream kconfig code.
>
> Yes, so given that there are two problematic changes:
>   - source statements in choices,
>   - environment variable direct expansion,
> I wonder if it makes sense for us to update our kconfig infra...
>
> Regards,
> Yann E. MORIN.
>

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot