From: Petr Vorel <petr.vorel@gmail.com>
To: Titouan Christophe <titouan.christophe@mind.be>
Cc: ps.report@gmx.net, yann.morin@orange.com,
thomas.petazzoni@bootlin.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/7] */Config.in: use the new $(VAR) syntax
Date: Sat, 17 Oct 2026 00:17:11 +0200 [thread overview]
Message-ID: <20261016221711.GD331129@pevik> (raw)
In-Reply-To: <20261010151121.876133-3-titouan.christophe@mind.be>
> Since upstream Linux commit 104daea149 [1], the syntax for Kconfig variable
> references requires to enclose them in $(VAR).
> Variables whose expansion should be deferred until makefile evaluation
> (such as TOPDIR, BASE_DIR, CONFIG_DIR or ARCH) must now be written as
> \$(VAR).
+1
> Finally, the `option env=` syntax will no longer be supported.
> Environment variables are directly expanded in KConfig files.
> Therefore, some intermediate variables that were used as "tricks" can be
> removed and their usage subsituted with the actual environment variable
> they were derived from. This changes the following:
> BR2_VERSION --> BR2_VERSION_FULL
> BR2_HOSTARCH --> HOSTARCH
> BR2_SKIP_LEGACY --> SKIP_LEGACY
> BR2_BASE_DIR --> BASE_DIR
> BR2_HOST_GCC_VERSION --> HOST_GCC_VERSION
> BR2_DEFCONFIG_FROM_ENV --> BR2_DEFCONFIG
> Also update the manual to reflect these new conventions
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=104daea149c45cc84842ce77a9bd6436d19f3dd8
LGTM, I'd add my RBT but the commit is broken:
$ make defconfig
Config.in:23: can't open file "(BASE_DIR)/.br2-external.in.paths"
make[1]: *** [Makefile:1047: defconfig] Error 1
make: *** [Makefile:83: _all] Error 2
Even removing output/ directory does not help:
$ rm -rf output/; make defconfig; echo $?
You fixed it in the 5th commit
04d878306a ("package/openssl: move libopenssl/libressl options out of the choice")
But NACK to that approach. Each commit must work. Either this 5th commit must be
squashed into with this 2nd commit, or if it does not break the current master
it should be as a separate commit before.
With that fixed you may add my RBT.
Kind regards,
Petr
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-10-16 22:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 15:11 [Buildroot] [PATCH 0/7] Update kconfig inrastructure to Linux 7.2.9 Titouan Christophe via buildroot
2026-10-10 15:11 ` [Buildroot] [PATCH 1/7] Makefile: always use a base config file for defconfig Titouan Christophe via buildroot
2026-10-16 21:30 ` Petr Vorel
2026-10-10 15:11 ` [Buildroot] [PATCH 2/7] */Config.in: use the new $(VAR) syntax Titouan Christophe via buildroot
2026-10-16 22:17 ` Petr Vorel [this message]
2026-10-10 15:11 ` [Buildroot] [PATCH 3/7] */Config.in: replace bool entries with prompt within all choices Titouan Christophe via buildroot
2026-10-16 22:25 ` Petr Vorel
2026-10-10 15:11 ` [Buildroot] [PATCH 5/7] package/openssl: move libopenssl/libressl options out of the choice Titouan Christophe via buildroot
2026-10-16 22:51 ` Petr Vorel
2026-10-10 15:11 ` [Buildroot] [PATCH 6/7] docs/manual: add migration notes for changes in the kconfig syntax Titouan Christophe via buildroot
2026-10-16 22:53 ` Petr Vorel
2026-10-10 15:11 ` [Buildroot] [PATCH 7/7] Makefile: add new target "yellowconfig" based on kconfiglib Titouan Christophe via buildroot
2026-10-16 21:44 ` Petr Vorel
2026-10-11 19:12 ` [Buildroot] [PATCH 0/7] Update kconfig inrastructure to Linux 7.2.9 Petr Vorel
2026-10-11 19:30 ` Titouan Christophe via buildroot
2026-10-16 21:29 ` Petr Vorel
[not found] ` <20261010151121.876133-5-titouan.christophe@mind.be>
2026-10-16 22:47 ` [Buildroot] [PATCH 4/7] support/kconfig: update to kconfig from " Petr Vorel
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=20261016221711.GD331129@pevik \
--to=petr.vorel@gmail.com \
--cc=buildroot@buildroot.org \
--cc=ps.report@gmx.net \
--cc=thomas.petazzoni@bootlin.com \
--cc=titouan.christophe@mind.be \
--cc=yann.morin@orange.com \
/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