public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Michael Hope <michael.hope@linaro.org>
To: crossgcc@sourceware.org
Subject: GCC support libraries and sysroot
Date: Fri, 23 Mar 2012 01:23:00 -0000	[thread overview]
Message-ID: <CANLjY-nNjr+7bQXdEhVdN5E-Tr05UKMVO7RAyCXLagzeJc0Nyg@mail.gmail.com> (raw)

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.

-- Michael

--
For unsubscribe information see http://sourceware.org/lists.html#faq

             reply	other threads:[~2012-03-23  1:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23  1:23 Michael Hope [this message]
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

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-nNjr+7bQXdEhVdN5E-Tr05UKMVO7RAyCXLagzeJc0Nyg@mail.gmail.com \
    --to=michael.hope@linaro.org \
    --cc=crossgcc@sourceware.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).