From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] External toolchain built by buildroot no longer supported.
Date: Tue, 6 Apr 2010 15:15:25 +0000 (UTC) [thread overview]
Message-ID: <hpfj6c$mpa$1@dough.gmane.org> (raw)
In-Reply-To: 87y6h0r5e9.fsf@macbook.be.48ers.dk
On 2010-04-06, Peter Korsgaard <jacmet@uclibc.org> wrote:
>>>>>> "Grant" == Grant Edwards <grant.b.edwards@gmail.com> writes:
>
> Grant> As of this commit
> Grant> http://git.buildroot.org/buildroot/commit/?id=3b7aee23f2ab732f06b8a090ca002fb102d547ee
>
> Grant> use of of external toolchains built by buildroot is no longer
> Grant> possible.
>
> Grant> Are we to assume that crosstool-NG is now the "officially supported"
> Grant> source for external toolchains?
>
> Long term I think users are better off with using crosstool-NG for
> their toolchains, as that has a more active development community.
That seems to be the case.
> The buildroot toolchains work, and I do small fixes / version
> updates, but noone is really doing active development on them.
>
> As an example, GDB 7.x is out since October, but still not in BR (I
> had a quick look, but didn't get it to work).
>
> With that said, I would very much like to support BR toolchains as
> external toolchains if it's possible without too many dirty hacks
> (sorry, haven't been following the recent discussion about it).
AFAICT, the recent commit relies on the assumption that both --prefix
and --sysroot values are correct and that the "prefix" is a child of
"sysroot".
That's not the case for buildroot toolchains. They have a prefix of
"/usr" and a sysroot pointing to the output/staging directory. I'm
guessing that setting the buildroot toolchain's --prefix value to
output/staging/usr should fix the problem, but I'm still a bit fuzzy
on how the recently committed change works.
> Besides the advantages you listed there's also the fact that it will
> make migration easier in the future - E.G.:
>
> BR with internal toolchain -> BR with external BR toolchain -> BR with
> crosstool-NG toolchain.
True.
--
Grant Edwards grant.b.edwards Yow! My mind is making
at ashtrays in Dayton ...
gmail.com
next prev parent reply other threads:[~2010-04-06 15:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 14:41 [Buildroot] External toolchain built by buildroot no longer supported Grant Edwards
2010-04-06 15:02 ` Peter Korsgaard
2010-04-06 15:15 ` Grant Edwards [this message]
2010-04-06 16:42 ` Yann E. MORIN
2010-04-06 18:19 ` Grant Edwards
2010-04-06 16:42 ` Yann E. MORIN
2010-04-06 18:10 ` Grant Edwards
2010-04-06 18:12 ` 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='hpfj6c$mpa$1@dough.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.