From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] External toolchain: crosstool-NG instead of buildroot?
Date: Fri, 18 Dec 2009 21:36:30 +0000 (UTC) [thread overview]
Message-ID: <hggsku$9gv$1@ger.gmane.org> (raw)
In-Reply-To: 20091218223139.2118763c@surf
On 2009-12-18, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Grant Edwards <grant.b.edwards@gmail.com> a ??crit :
>
>> The buildroot docs recommends using crosstool-NG to generate
>> external toolchains.
>>
>> Is there some reason one shouldn't or can't use a toolchain
>> generated buildroot?
>
> Theorically, Buildroot should work just as fine as Crosstool-NG for
> generating toolchain.
So far it seems to be working fine. I haven't figured out what
the minimal set of required files is. Initially I took a
snapshot of everything under output/staging. Subsequent makes
using that as an external toolchain failed because it found
files in output/staging/usr/share that it didn't expect to be
there. I removed usr/share from my "toolchain", and now builds
seem to work fine.
> In practive, my own *personal* feeling is that the Crosstool-NG
> community is spending more time to improve this toolchain generation
> tool than the Buildroot community spends on the toolchain part. I have
> the impression that they do a better job at following new upstream
> versions, integrating necessary patches, etc. But again, I have no
> objective facts to validate these feelings.
For now I think I'll stick with a buildroot-generated toolchain.
--
Grant Edwards grante Yow! I'm having a
at tax-deductible experience!
visi.com I need an energy crunch!!
next prev parent reply other threads:[~2009-12-18 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 13:00 [Buildroot] External toolchain: crosstool-NG instead of buildroot? Grant Edwards
2009-12-18 21:31 ` Thomas Petazzoni
2009-12-18 21:36 ` Grant Edwards [this message]
2009-12-20 19:50 ` Peter Korsgaard
2009-12-20 21:37 ` Yann E. MORIN
2009-12-21 20:06 ` Peter Korsgaard
2009-12-21 22:10 ` Yann E. MORIN
2009-12-22 7:54 ` 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='hggsku$9gv$1@ger.gmane.org' \
--to=grant.b.edwards@gmail.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