From: William Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] external toolchain question
Date: Wed, 15 Sep 2010 19:17:03 +0100 [thread overview]
Message-ID: <4C910D9F.2060308@carallon.com> (raw)
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?
Thanks
Will
--
------------------------------------------------------------------------
Will Wagner will_wagner at carallon.com
Development Manager Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
next reply other threads:[~2010-09-15 18:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 18:17 William Wagner [this message]
2010-09-15 18:40 ` [Buildroot] external toolchain question Marcus Osdoba
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=4C910D9F.2060308@carallon.com \
--to=will_wagner@carallon.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