From: Peter Seiderer via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@busybox.net, "Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH v1 0/8] support/kconfig: bump to linux-v6.9-rc5 version
Date: Wed, 8 May 2024 17:16:29 +0200 [thread overview]
Message-ID: <20240508171629.55ae5111@gmx.net> (raw)
In-Reply-To: <20240506210440.323ccb15@windsurf>
Hello Thomas,
On Mon, 6 May 2024 21:04:40 +0200, Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:
> Hello,
>
> On Mon, 6 May 2024 16:45:43 +0200
> Peter Seiderer via buildroot <buildroot@buildroot.org> wrote:
>
> > The patches are orderd by the first 5 handling some minor nits (result of
> > the new kconfig beeing a little more strict about the syntax, can be
> > applied in advance):
> >
> > - boot/barebox/Config.in: source argument needs quotation marks
> > - package/cmocka/Config.in: bool argument needs quotation marks
> > - package/dovecot/Config.in: source argument needs quotation marks
> > - package/python-pydal/Config.in: bool argument needs quotation marks
> > - package/x11r7/Config.in: source argument needs quotation marks
>
> I have applied those preparation patches that make sense regardless of
> what happens with the bump.
Thanks...
>
> > 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).
Yes, but the next two patches can eventually squashed with this one, but did
keep separate for better patch review/iteration (suspected some more
discussion on this ones)...
>
> > 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? I remember Yann saying that this was
> a problematic change for us in the upstream kconfig code.
Yes, that is the reasoning for the (suggested by Yann)
patches/23-Revert-kconfig-allow-only-config-comment-and-if-insi.patch
With this one reverted I get the following warnings/errors:
toolchain/toolchain-external/Config.in:12: syntax error
toolchain/toolchain-external/Config.in:12: invalid statement
toolchain/toolchain-external/Config.in:13: invalid statement
toolchain/toolchain-external/Config.in:16: invalid statement
toolchain/toolchain-external/Config.in:17: invalid statement
toolchain/toolchain-external/Config.in:20: invalid statement
toolchain/toolchain-external/Config.in:23: invalid statement
toolchain/toolchain-external/Config.in:24: invalid statement
toolchain/toolchain-external/Config.in:27: invalid statement
toolchain/toolchain-external/Config.in:30: invalid statement
toolchain/toolchain-external/Config.in:33: invalid statement
toolchain/toolchain-external/Config.in:38: invalid statement
toolchain/toolchain-external/Config.in:41: invalid statement
system/Config.in:23: syntax error
system/Config.in:23: invalid statement
system/Config.in:157: syntax error
system/Config.in:157: invalid statement
package/openssl/Config.in:46: syntax error
package/openssl/Config.in:46: invalid statement
package/jpeg/Config.in:43: syntax error
package/jpeg/Config.in:43: invalid statement
With the patch the remaining problematic source-inside-choice are
in package/openssl/Config.in, seems not all content is allowed
to be included...
Regards,
Peter
>
> Best regards,
>
> Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-05-08 15:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 14:45 [Buildroot] [PATCH v1 0/8] support/kconfig: bump to linux-v6.9-rc5 version Peter Seiderer via buildroot
2024-05-06 14:45 ` [Buildroot] [PATCH v1 1/8] boot/barebox/Config.in: source argument needs quotation marks Peter Seiderer via buildroot
2024-05-26 20:45 ` Peter Korsgaard
2024-05-06 14:45 ` [Buildroot] [PATCH v1 2/8] package/cmocka/Config.in: bool " Peter Seiderer via buildroot
2024-05-26 20:46 ` Peter Korsgaard
2024-05-06 14:45 ` [Buildroot] [PATCH v1 3/8] package/dovecot/Config.in: source " Peter Seiderer via buildroot
2024-05-26 20:46 ` Peter Korsgaard
2024-05-06 14:45 ` [Buildroot] [PATCH v1 4/8] package/python-pydal/Config.in: bool " Peter Seiderer via buildroot
2024-05-26 20:45 ` Peter Korsgaard
2024-05-06 14:45 ` [Buildroot] [PATCH v1 5/8] package/x11r7/Config.in: source " Peter Seiderer via buildroot
2024-05-26 20:46 ` Peter Korsgaard
2024-05-06 14:45 ` [Buildroot] [PATCH v1 6/8] support/kconfig: bump to linux-v6.9-rc5 version Peter Seiderer via buildroot
2024-05-08 21:41 ` Petr Vorel
2024-05-08 21:54 ` Peter Seiderer via buildroot
2024-05-09 10:51 ` Yann E. MORIN
2024-05-06 14:45 ` [Buildroot] [PATCH v1 7/8] support/kconfig: reference environment variables directly (remove 'option env=') Peter Seiderer via buildroot
2024-05-06 19:06 ` Thomas Petazzoni via buildroot
2024-05-08 14:53 ` Peter Seiderer via buildroot
2024-05-08 19:18 ` Yann E. MORIN
2024-05-06 14:45 ` [Buildroot] [PATCH v1 8/8] package/openssl: move libopenssl/libressl source statemetns outside of the choice Peter Seiderer via buildroot
2024-05-06 20:11 ` Yann E. MORIN
2024-05-08 15:07 ` Peter Seiderer via buildroot
2024-05-08 18:57 ` Yann E. MORIN
2024-05-06 19:04 ` [Buildroot] [PATCH v1 0/8] support/kconfig: bump to linux-v6.9-rc5 version Thomas Petazzoni via buildroot
2024-05-06 20:19 ` Yann E. MORIN
2024-05-06 20:21 ` Thomas Petazzoni via buildroot
2024-05-08 15:21 ` Peter Seiderer via buildroot
2024-05-08 19:08 ` Yann E. MORIN
2024-05-08 15:16 ` Peter Seiderer via buildroot [this message]
2025-05-18 14:55 ` Thomas Petazzoni via buildroot
2025-05-21 7:40 ` Peter Seiderer via buildroot
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=20240508171629.55ae5111@gmx.net \
--to=buildroot@buildroot.org \
--cc=buildroot@busybox.net \
--cc=ps.report@gmx.net \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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