From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] External toolchain support improvements
Date: Mon, 03 Nov 2008 11:15:27 +0100 [thread overview]
Message-ID: <874p2pm7y8.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20081030094501.66983ff9@surf> (Thomas Petazzoni's message of "Thu\, 30 Oct 2008 09\:45\:01 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> Improve external toolchain support
Thomas> * Do not put kernel-headers in the dependencies of BASE_TARGETS in
Thomas> the case where BR2_TOOLCHAIN_SOURCE is not y. The kernel headers
Thomas> are already supposed to be part of the external toolchain, so
Thomas> there's no need to download, extract and install them.
Sounds good.
Thomas> * In the configuration system, don't display the kernel headers
Thomas> version selection list when an external toolchain is selected. This
Thomas> is implemented by moving the source
Thomas> "toolchain/kernel-headers/Config.in" inside the if
Thomas> BR2_TOOLCHAIN_SOURCE in toolchain/Config.in.2.
And this too.
Thomas> * Change the description and help message of the BR2_LARGEFILE,
Thomas> BR2_INET_IPV6, BR2_INET_RPC, and BR2_SOFT_FLOAT option in
Thomas> toolchain/external-toolchain/Config.in. In the case of an external
Thomas> toolchain, the semantic of these options is not to enable large
Thomas> file support, IPV6 or RPC (since the toolchain is already compiled,
Thomas> it has been decided previously). Their semantic is to let Buildroot
Thomas> know about the characteristics of the external toolchain being
Thomas> used.
Exactly.
Thomas> As an improvement, we could guess these values automatically:
Thomas> - for BR2_LARGEFILE, look at the value of __UCLIBC_HAS_LFS__ in
Thomas> bits/uClibc_config.h in the libc headers directory.
This would only work for external toolchains using uclibc - I guess
the main reason for using an external toolchain is to not use uclibc?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-11-03 10:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 8:45 [Buildroot] External toolchain support improvements Thomas Petazzoni
2008-10-31 18:42 ` hartleys
2008-11-03 8:31 ` Thomas Petazzoni
2008-11-03 15:52 ` hartleys
2008-11-03 23:51 ` Markus Heidelberg
2008-10-31 19:21 ` Grant Likely
2008-11-03 10:15 ` Peter Korsgaard [this message]
2008-11-03 10:18 ` Peter Korsgaard
2008-11-03 12:48 ` Shinya Kuribayashi
2008-11-03 12:58 ` Peter Korsgaard
2008-11-03 13:25 ` Shinya Kuribayashi
2008-11-03 14:03 ` Peter Korsgaard
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=874p2pm7y8.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