From: Marcus Osdoba <marcus.osdoba@googlemail.com>
To: buildroot@busybox.net
Subject: [Buildroot] external toolchain question
Date: Wed, 15 Sep 2010 20:40:54 +0200 [thread overview]
Message-ID: <4C911336.6060003@googlemail.com> (raw)
In-Reply-To: <4C910D9F.2060308@carallon.com>
Am 15.09.2010 20:17, schrieb William Wagner:
> Hello,
>
> I'm trying to get a crosstool-ng toolchain working and running into a
> few problems. One thing I found with c++ support was that libstdc++
> was being copied into target/usr/lib but it was located in staging/lib.
>
> It seems like this commit
> http://git.buildroot.net/buildroot/commit/?id=ecb7642cce36bc68d93f0eee677adc7da538228d
> explicitly moved it in the target. The comment appears to be for an
> external buildroot toolchain not a crosstools toochain. Is that why it
> works for some people? For my crosstools toolchain it seemed that
> moving it fixed my problem.
>
> As an aside what is the status of using a buildroot generated
> toolchain as an external toolchain? Any instructions anywhere on how
> to do it?
>
Hi Will,
I asked a similar questions some time before. Grant answered to my
question "preserve toolchain", that he didn't manage to recycle the
buildroot generated toolchain for a second run in an easy way. So it
seems, that you are forced to from scratch including the toolchain if
you do not use a "complete" external toolchain (e.g. generated with
crosstool-ng).
Personally I didn't yet try out crosstool-ng because the current
patchlevel of buildroot is a higher one (e.g. gcc 4.3.4 vs 4.3.5).
Regards,
Marcus
next prev parent reply other threads:[~2010-09-15 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 18:17 [Buildroot] external toolchain question William Wagner
2010-09-15 18:40 ` Marcus Osdoba [this message]
2010-09-15 18:50 ` Yann E. MORIN
2010-09-15 19:33 ` Marcus Osdoba
2010-09-15 20:46 ` Yann E. MORIN
2010-09-15 19:19 ` Thomas Petazzoni
2010-09-16 8:03 ` William Wagner
2010-09-16 9:04 ` Thomas Petazzoni
2010-09-16 11:41 ` William Wagner
2010-09-16 12:14 ` 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=4C911336.6060003@googlemail.com \
--to=marcus.osdoba@googlemail.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.