From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] auto-detecting toolchain metadata?
Date: Tue, 22 Nov 2016 16:49:17 +0100 [thread overview]
Message-ID: <20161122164917.3ee6e506@free-electrons.com> (raw)
In-Reply-To: <ca906326-1a51-56db-7411-dcf5408c9255@mentor.com>
Hello,
On Tue, 22 Nov 2016 07:44:57 -0800, Hollis Blanchard wrote:
> My defconfig contains this:
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y
> BR2_TOOLCHAIN_EXTERNAL_CUSTOM_PREFIX="$(ARCH)-linux-gnu"
> BR2_TOOLCHAIN_EXTERNAL_GCC_4_9=y
> BR2_TOOLCHAIN_EXTERNAL_HEADERS_3_7=y
> BR2_TOOLCHAIN_EXTERNAL_CUSTOM_GLIBC=y
> BR2_TOOLCHAIN_EXTERNAL_CXX=y
>
> There are no other toolchain-related options (prefixed with
> BR2_TOOLCHAIN or otherwise). Can you elaborate on why I can't just
> replace these?
Hum, right we're talking only about external toolchains, and only about
a defconfig. So indeed, all options should start with
BR2_TOOLCHAIN_EXTERNAL_.
Still, I find a tool that replaces/edits stuff in an existing defconfig
to be somewhat confusing. Something that generates a defconfig fragment
seems a lot clearer to understand for new users.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-22 15:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 18:39 [Buildroot] auto-detecting toolchain metadata? Hollis Blanchard
2016-11-01 18:46 ` Yann E. MORIN
2016-11-01 20:27 ` Thomas Petazzoni
2016-11-22 1:04 ` Hollis Blanchard
2016-11-22 8:29 ` Thomas Petazzoni
2016-11-22 15:44 ` Hollis Blanchard
2016-11-22 15:49 ` Thomas Petazzoni [this message]
2016-11-22 16:12 ` Hollis Blanchard
2016-11-22 16:21 ` Thomas Petazzoni
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=20161122164917.3ee6e506@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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