From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Busybox build fails on raspberrypi defconfig
Date: Thu, 18 Jun 2015 18:08:13 +0200 [thread overview]
Message-ID: <5582ECED.8030205@mind.be> (raw)
In-Reply-To: <20150618110211.2bc21e04@free-electrons.com>
On 06/18/15 11:02, Thomas Petazzoni wrote:
[snip]
> I told you in my previous e-mail, but maybe it wasn't clear. It's due
> to a kconfig limitation/bug. Basically, here is the scenario:
>
> * You start from a fresh configuration.
>
> * You select uClibc 0.9.33, and exit menuconfig.
>
> * Automatically, the file package/uclibc/uClibc-0.9.33.config is used
> as the uclibc configuration file (option BR2_UCLIBC_CONFIG)
>
> * Now, you go back to menuconfig, and you decide to switch to
> uClibc-ng.
>
> -> And now, instead of automatically switching to
> package/uclibc/uClibc-ng.config, package/uclibc/uClibc-0.9.33.config is
> kept as the value of BR2_UCLIBC_CONFIG. This is the limitation of
> kconfig I'm talking about above.
[snip]
> One way we could get around this problem is by making the
> BR2_UCLIBC_CONFIG option visible only if the user selects another
> option like "Use a custom uClibc configuration file".
Or let the default be empty, and choose a default from the .mk file when it's
empty. But we've discussed that before and some people didn't like it.
Note: this applies for all string options for which we have multiple defaults:
BR2_TARGET_GRUB2_BUILTIN_MODULES, BR2_TARGET_ROOTFS_ISO9660_BOOT_MENU.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2015-06-18 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 13:27 [Buildroot] Busybox build fails on raspberrypi defconfig Johan Oudinet
2015-06-17 14:02 ` Johan Oudinet
2015-06-17 14:41 ` Thomas Petazzoni
2015-06-18 8:54 ` Johan Oudinet
2015-06-18 9:02 ` Thomas Petazzoni
2015-06-18 16:08 ` Arnout Vandecappelle [this message]
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=5582ECED.8030205@mind.be \
--to=arnout@mind.be \
--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