From: Michael Hope <michael.hope@linaro.org>
To: Maurizio Vitale <mrz.vtl@gmail.com>
Cc: crossgcc@sources.redhat.com
Subject: Re: GCC support libraries and sysroot
Date: Fri, 20 Jul 2012 03:56:00 -0000 [thread overview]
Message-ID: <CANLjY-mW=7beWtyLKm-OWvTpFPsMppA0an5Tff0newzYAZsdWg@mail.gmail.com> (raw)
In-Reply-To: <loom.20120715T183355-394@post.gmane.org>
On 16 July 2012 04:40, Maurizio Vitale <mrz.vtl@gmail.com> wrote:
> Michael Hope <michael.hope <at> linaro.org> writes:
>
>>
>> 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.
>>
>> For our binary builds we plan to supply a few different sysroots
>> including a minimal libc, developer image with GTK and X, and a
>> desktop image with a wide range of packages. They'll come as tarballs
>> and the intent is for people to delete the old $tuple/$sysroot and
>> extract the new one in its place. Currently this means that the
>> support libraries will also get deleted. The target comes with these
>> libraries preinstalled.
>>
>
> I'm exploring similar sysroot setups (but in my case I want the sysroot to work
> for both gcc and clang). Other than size, what would go wrong with having all
> sysroots including the GCC's support libraries and whatever additional library
> the specific sysroot introduces?
> Obviously it would require redistribution of all sysroot tarfiles whenever the
> compiler toolchain changes, but other than that and size, I don't see problems.
> I've just started with this setup, so I might be missing the obvious.
Hi Maurizio. We release monthly so the cost would be unfortunate.
-- Michael
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2012-07-17 3:59 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
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 [this message]
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='CANLjY-mW=7beWtyLKm-OWvTpFPsMppA0an5Tff0newzYAZsdWg@mail.gmail.com' \
--to=michael.hope@linaro.org \
--cc=crossgcc@sources.redhat.com \
--cc=mrz.vtl@gmail.com \
/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).