From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Copying extra libs into image using external toolchain
Date: Sat, 6 Feb 2010 17:02:38 +0100 [thread overview]
Message-ID: <20100206170238.345e1bd8@surf> (raw)
In-Reply-To: <1265241688.2045.48.camel@coalu.atr>
On Thu, 04 Feb 2010 01:01:28 +0100
Lionel Landwerlin <llandwerlin@gmail.com> wrote:
> With external toolchains, buildroot assumes that libstdc++ is
> installed in $(SYSROOT)/lib/ which isn't always the case.
> For example the STLinux toolchain has its libstdc++ installed in
> $(SYSROOT)/usr/lib like your toolchain.
Yes, correct.
> We should rather fix the buildroot script that copies the libraries
> than adding extra scripts outside of buildroot. It's in
> toolchain/external-toolchain/ext-tool.mk
This is something I already have a patch for in my
codesourcery-toolchain-support branch:
http://git.buildroot.net/~tpetazzoni/git/buildroot/commit/?h=codesourcery-toolchain-support&id=e6eec872c5720be4438f1d0db28f69ed50620b58
Unfortunately, the changes needed to get the libraries from either /lib
or /usr/lib are mixed with other changes related to multilib support,
and these latter changes are not ready for submission.
I'll try to split the /lib - /usr/lib thing from the rest and submit a
proper patch.
Cheers,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-02-06 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 23:07 [Buildroot] Copying extra libs into image using external toolchain Cameron Hutchison
2010-02-03 0:04 ` Grant Edwards
2010-02-03 22:13 ` Cameron Hutchison
2010-02-04 0:01 ` Lionel Landwerlin
2010-02-06 16:02 ` Thomas Petazzoni [this message]
2010-02-08 5:38 ` Cameron Hutchison
2010-02-08 6:34 ` Cameron Hutchison
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=20100206170238.345e1bd8@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