From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Michael Hope <michael.hope@linaro.org>
Cc: crossgcc@sourceware.org
Subject: Re: GCC support libraries and sysroot
Date: Sun, 06 May 2012 16:37:00 -0000 [thread overview]
Message-ID: <20120506183641.5d26bcb4@skate> (raw)
In-Reply-To: <CANLjY-nNjr+7bQXdEhVdN5E-Tr05UKMVO7RAyCXLagzeJc0Nyg@mail.gmail.com>
Hello Michael,
Le Fri, 23 Mar 2012 14:22:55 +1300,
Michael Hope <michael.hope@linaro.org> a écrit :
> Hi there. Why does crosstool-NG create a symlink from
> $tuple/$sysroot/lib to $tuple/lib? It causes GCC to install support
> libraries like libgcc_s.so into the sysroot instead of the default
> location which makes it tricky to replace the sysroot later.
On the other hand, this was making things simple and easy for tools
like Buildroot to leverage the pre-built Linaro toolchains. The Linaro,
Sourcery CodeBench, Crosstool-NG and Buildroot toolchains all behaved
the same by installing all the libraries into the sysroot, so it was
easy to support all of them: we just copy the complete sysroot into a
"staging" directory, into which we add more libraries/headers as we
build stuff for the target.
Since Linaro 2012.03 (and therefore 2012.04), this simple idea doesn't
work anymore as Linaro toolchains have important stuff installed
outside of the sysroot, which makes it a lot more complicated for
Buildroot to handle (and I guess possibly other similar tools).
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2012-05-06 16:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 1:23 Michael Hope
2012-03-23 6:27 ` Building armv7 "cross-native" GCC Douglas Jerome
2012-03-25 14:37 ` GCC support libraries and sysroot Yann E. MORIN
2012-03-25 15:16 ` Paul Smith
2012-03-25 18:28 ` Khem Raj
2012-03-25 19:26 ` Michael Hope
2012-05-06 16:37 ` Thomas Petazzoni [this message]
2012-05-06 20:24 ` Michael Hope
2012-05-09 8:26 ` Thomas Petazzoni
2012-07-16 8:03 ` Maurizio Vitale
2012-07-20 3:56 ` Michael Hope
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=20120506183641.5d26bcb4@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=crossgcc@sourceware.org \
--cc=michael.hope@linaro.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).