From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] staging_dir/usr/lib vs staging_dir/lib
Date: Thu, 2 Aug 2007 10:34:55 +0200 [thread overview]
Message-ID: <20070802083455.GI11697@aon.at> (raw)
In-Reply-To: <1185947996.20419.8.camel@localhost.localdomain>
On Wed, Aug 01, 2007 at 07:59:56AM +0200, Hans-Christian Egtvedt wrote:
>Weird, because staging_dir/usr is a symlink to staging_dir/.
This means that you don't use a toolchain that supports sysroot.
For non-sysroot enabled toolchains we currently symlink staging_dir/usr
to staging_dir because the old, deprecated gcc had quite some trouble
otherwise and i don't care to fix them up (since the current stable
series of gcc work fine for me).
Please note that i, personally didn't enable sysroot support for 4.0.x
but skhill did (IIRC) so you're better off to use 4.2.1 for this.
next prev parent reply other threads:[~2007-08-02 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 18:38 [Buildroot] staging_dir/usr/lib vs staging_dir/lib Christopher Reder
2007-08-01 5:59 ` Hans-Christian Egtvedt
2007-08-01 7:48 ` [Buildroot] [PATCH] " Hans-Christian Egtvedt
2007-08-02 8:34 ` Bernhard Fischer [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-02 13:37 [Buildroot] " Ulf Samuelsson
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=20070802083455.GI11697@aon.at \
--to=rep.dot.nop@gmail.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