From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] busybox, hardcoded config
Date: Fri, 24 Dec 2010 14:22:52 +0100 [thread overview]
Message-ID: <87zkrvqp8z.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20101223073318.154656bz82tuap44@www.home.zuerker.org> (Heiko Zuerker's message of "Thu, 23 Dec 2010 07:33:18 -0600")
>>>>> "Heiko" == Heiko Zuerker <heiko@zuerker.org> writes:
Heiko> Hey,
Heiko> there was recently a discussion on the topic of automatically turning
Heiko> on specific kernel features, which can cause some problems.
Heiko> This is very heavily done in busybox, i.e. nfs support for mount keeps
Heiko> being turned on by the makefile. At least in my case this is causing
Heiko> me some grief.
Hmm, why is that? Presumably you want to be able to mount NFS shares if
you enable RPC support in the toolchain?
We could remove the enable part of the NFS setting though (so only
disable if no RPC support to not get a build error), and just enable it
in the default config.
Heiko> I think we really should keep this automatically setting of
Heiko> configurations to an absolute minimum. Can't we rely on the person
Heiko> configuring buildroot, to set the correct options he or she needs for
Heiko> example in busybox or the kernel?
Agreed. We shouldn't tweak configs behind the users back more than
absolutely necessary. Busybox is a bit special in the sense that we want
to use a single default config, but some options depends on how the
toolchain is configured.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2010-12-24 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 13:33 [Buildroot] busybox, hardcoded config Heiko Zuerker
2010-12-24 7:52 ` Thomas Petazzoni
2010-12-24 13:29 ` Heiko Zuerker
2010-12-25 22:03 ` Peter Korsgaard
2010-12-26 14:08 ` Heiko Zuerker
2010-12-27 15:28 ` Peter Korsgaard
2010-12-27 15:34 ` Heiko Zuerker
2010-12-27 15:46 ` Peter Korsgaard
2010-12-24 13:22 ` Peter Korsgaard [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=87zkrvqp8z.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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