From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] core/pkg-kconfig: add an option to use olddefconfig
Date: Sat, 26 Mar 2016 18:42:03 +0100 [thread overview]
Message-ID: <20160326174203.GA3589@free.fr> (raw)
In-Reply-To: <1458901049-3693-1-git-send-email-romain.izard.pro@gmail.com>
Romain, All,
On 2016-03-25 11:17 +0100, Romain Izard spake thusly:
> Using 'yes "" | make oldconfig' to regenerate a .config file from an
> existing defconfig does not work reliably in all cases. Specifically, it
> does not work well with tristate choice entries.
>
> The correct way to do it is to use 'make olddefconfig', but this target
> is not supported in projects that use an old version of kconfig. As
> most projects do not use tristate entries, there is no need for them to
> upgrade.
>
> As a result, add support in the pkg-kconfig infrastructure for both
> cases, with a configuration entry to select which mode to use.
In fact, we've already discussed this, and we concluded that we would
want an automatic behaviour.
I.e. we try to use olddefconfig, and fallback to the yes-trick, like so:
make olddefconfig || { yes "" |make oldconfig; }
Care to adapt your patch and respin, please? Of course, your second
patch will no longer make sense after that.
In the meantime, I marked your patches as "Changes Requested" in
patchwork.
Thanks! ;-)
Regards,
Yann E. MORIN.
> Signed-off-by: Romain Izard <romain.izard.pro@gmail.com>
> ---
> docs/manual/adding-packages-kconfig.txt | 5 +++++
> package/pkg-kconfig.mk | 10 ++++++----
> 2 files changed, 11 insertions(+), 4 deletions(-)
>
> diff --git a/docs/manual/adding-packages-kconfig.txt b/docs/manual/adding-packages-kconfig.txt
> index 3290024..50c4ecb 100644
> --- a/docs/manual/adding-packages-kconfig.txt
> +++ b/docs/manual/adding-packages-kconfig.txt
> @@ -53,6 +53,11 @@ It is mandatory to provide either, but not both:
> * +FOO_KCONFIG_FILE+ specifies the path to a defconfig or full-config file
> to be used to configure the package.
>
> +* +FOO_KCONFIG_OLDDEFCONFIG+ when set specifies that the 'make' rule to
> + call with defconfig files is 'olddefconfig'. Only some projects support
> + it, but the default rule called 'oldconfig' can misbehave when the
> + config file changes tristate 'choice' entries.
> +
> * +FOO_KCONFIG_DEFCONFIG+ specifies the defconfig 'make' rule to call to
> configure the package.
>
> diff --git a/package/pkg-kconfig.mk b/package/pkg-kconfig.mk
> index 90f3f9f..71c6865 100644
> --- a/package/pkg-kconfig.mk
> +++ b/package/pkg-kconfig.mk
> @@ -60,8 +60,7 @@ $$($(2)_KCONFIG_FILE) $$($(2)_KCONFIG_FRAGMENT_FILES): | $(1)-patch
> # The specified source configuration file and any additional configuration file
> # fragments are merged together to .config, after the package has been patched.
> # Since the file could be a defconfig file it needs to be expanded to a
> -# full .config first. We use 'make oldconfig' because this can be safely
> -# done even when the package does not support defconfigs.
> +# full .config first.
> $$($(2)_DIR)/.config: $$($(2)_KCONFIG_FILE) $$($(2)_KCONFIG_FRAGMENT_FILES)
> $$(if $$($(2)_KCONFIG_DEFCONFIG), \
> $$($(2)_MAKE_ENV) $$(MAKE) -C $$($(2)_DIR) \
> @@ -69,8 +68,11 @@ $$($(2)_DIR)/.config: $$($(2)_KCONFIG_FILE) $$($(2)_KCONFIG_FRAGMENT_FILES)
> cp $$($(2)_KCONFIG_FILE) $$(@))
> support/kconfig/merge_config.sh -m -O $$(@D) \
> $$(@) $$($(2)_KCONFIG_FRAGMENT_FILES)
> - $$(Q)yes "" | $$($(2)_MAKE_ENV) $$(MAKE) -C $$($(2)_DIR) \
> - $$($(2)_KCONFIG_OPTS) oldconfig
> + $$(if $$($(2)_KCONFIG_OLDDEFCONFIG), \
> + $$($2_MAKE_ENV) $$(MAKE) -C $$($(2)_DIR) \
> + $$($(2)_KCONFIG_OPTS) olddefconfig, \
> + $$(Q)yes "" | $$($(2)_MAKE_ENV) $$(MAKE) -C $$($(2)_DIR) \
> + $$($(2)_KCONFIG_OPTS) oldconfig)
>
> # If _KCONFIG_FILE or _KCONFIG_FRAGMENT_FILES exists, this dependency is
> # already implied, but if we only have a _KCONFIG_DEFCONFIG we have to add
> --
> 2.5.0
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-03-26 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 10:17 [Buildroot] [PATCH 1/2] core/pkg-kconfig: add an option to use olddefconfig Romain Izard
2016-03-25 10:17 ` [Buildroot] [PATCH 2/2] linux: use olddefconfig with defconfig files Romain Izard
2016-03-26 17:42 ` Yann E. MORIN [this message]
2016-03-26 17:52 ` [Buildroot] [PATCH 1/2] core/pkg-kconfig: add an option to use olddefconfig Thomas Petazzoni
2016-03-29 8:39 ` Romain Izard
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=20160326174203.GA3589@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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