From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/device
Date: Fri, 14 Nov 2008 11:12:59 +0100 [thread overview]
Message-ID: <20081114111259.5e2d902c@surf> (raw)
In-Reply-To: <20081114100645.192BD3C8EE@busybox.net>
Le Fri, 14 Nov 2008 02:06:45 -0800 (PST),
jacmet at uclibc.org a ?crit :
> Modified:
> trunk/buildroot/target/device/Config.in.toolchain
I don't really get what's all this toolchain-related stuff in
target/device/. Even when using a binary external toolchain, all the
BR2_EXT_GCC_VERSION_* variables are set:
BR2_EXT_GCC_VERSION_4_1_2=y
BR2_EXT_GCC_VERSION_4_2_1=y
BR2_EXT_GCC_VERSION_4_2_2=y
BR2_EXT_GCC_VERSION_4_2_3=y
BR2_EXT_BINUTILS_VERSION_2_17=y
BR2_EXT_UCLIBC_VERSION_0_9_29=y
BR2_EXT_UCLIBC_VERSION_0_9_28_3=y
which looks a bit odd to me, since Buildroot has absolutely no power
over the version of the components used in an already compiled binary
toolchain.
And why is all that stuff implemented in target/device/ and not in
toolchain/ ?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2008-11-14 10:12 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 10:06 [Buildroot] svn commit: trunk/buildroot/target/device jacmet at uclibc.org
2008-11-14 10:12 ` Thomas Petazzoni [this message]
2008-11-14 11:15 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2009-01-29 17:28 ulf at uclibc.org
2009-01-29 17:26 ulf at uclibc.org
2009-01-29 17:23 ulf at uclibc.org
2009-01-29 17:22 ulf at uclibc.org
2009-01-29 17:22 ulf at uclibc.org
2009-01-29 17:21 ulf at uclibc.org
2009-01-29 19:04 ` Peter Korsgaard
2009-01-29 22:06 ` Ulf Samuelsson
2008-07-05 21:57 ulf at uclibc.org
2008-07-05 6:37 ulf at uclibc.org
2008-07-05 6:47 ` Thiago A. Corrêa
2008-07-05 11:42 ` Ulf Samuelsson
2008-07-07 6:09 ` Hans-Christian Egtvedt
2008-07-03 8:29 ulf at uclibc.org
2008-03-19 7:26 ulf at uclibc.org
2007-12-17 13:14 vanokuten at uclibc.org
2007-09-29 20:47 ulf at uclibc.org
2007-09-29 19:46 aldot at uclibc.org
2007-09-25 22:04 aldot at uclibc.org
2007-09-25 22:39 ` Ulf Samuelsson
2007-09-25 21:40 aldot at uclibc.org
2007-09-17 9:26 ulf at uclibc.org
2007-09-17 7:55 aldot at uclibc.org
2007-09-17 8:03 ` Hans-Christian Egtvedt
2007-09-17 8:38 ` Bernhard Fischer
2007-09-17 10:41 ` Ulf Samuelsson
2007-09-17 10:43 ` Ulf Samuelsson
2007-09-17 9:27 ` Bernhard Fischer
2007-09-17 12:16 ` Ulf Samuelsson
2007-09-17 11:10 ` Bernhard Fischer
2007-09-17 14:56 ` Ulf Samuelsson
2007-09-17 13:41 ` Bernhard Fischer
2007-09-18 6:54 ` Ulf Samuelsson
2007-08-19 18:26 ulf at uclibc.org
2007-08-01 9:06 ulf at uclibc.org
2007-07-31 22:57 ulf at uclibc.org
2007-07-31 15:39 aldot at uclibc.org
2007-07-31 15:37 aldot at uclibc.org
2007-03-18 11:53 aldot at uclibc.org
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=20081114111259.5e2d902c@surf \
--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