From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: Gstreamer and rpath
Date: Sun, 05 Aug 2007 12:29:01 +0100 [thread overview]
Message-ID: <1186313341.5962.32.camel@localhost.localdomain> (raw)
In-Reply-To: <46B2F6B9.7050605@klever.net>
On Fri, 2007-08-03 at 11:34 +0200, Michael Krelin wrote:
> >>> I'm actually semi against forcing staging to look like an image. The
> >>> fact gcc requires this for its sysroot option is a sign that they
> >>> haven't got this right yet.
> >>>
> >> Why?
> >
> > Well, why should I put libs in a /usr/lib directory rather that /lib? I
> > know there are guidelines but guidelines are one thing, forcing layouts
> > is a different thing.
>
> Good question, thought doesn't have much to do with sysroot facility.
> You have exactly the same freedom like you would have with no sysroot,
> you're free to install in /usr, in / or in /do-not-enforce-layout/
> prefix. The only difference is that you don't have to adjust your paths
> to take staging prefix into account and you are not likey to pick up
> your host system stuff while compiling.
>
> About getting 'sysroot' right... Doesn't the name imply using in sysroot
> the same layout like you would otherwise?
No, as I understand it sysroot makes assumptions about where the files
live under it. It assumes "/lib" and "/usr/lib" and its those
assumptions which I dislike. I haven't seen a way to change them but I
could easily be missing something.
If gcc does change them based on the values of prefix, libdir etc when
compiled, that would be a bit better but its still hardcoding things
into the compiler which I don't think should be hardcoded there. Does
anyone know if it adapts to changes in prefix. libdir and friends?
Regards,
Richard
next prev parent reply other threads:[~2007-08-05 11:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 6:10 Gstreamer and rpath Koen Kooi
2007-08-02 10:50 ` Michael Krelin
2007-08-02 11:23 ` Stanislav Brabec
2007-08-02 11:59 ` Michael Krelin
2007-08-02 12:38 ` Stanislav Brabec
2007-08-02 12:40 ` Philip Balister
2007-08-02 12:58 ` Michael Krelin
2007-08-02 13:27 ` Stanislav Brabec
2007-08-02 13:47 ` Koen Kooi
2007-08-02 14:15 ` Stanislav Brabec
2007-08-02 14:20 ` Koen Kooi
2007-08-02 14:47 ` Stanislav Brabec
2007-08-02 15:26 ` Michael Krelin
2007-08-02 15:46 ` Koen Kooi
2007-08-02 15:52 ` Michael Krelin
2007-08-02 17:00 ` Koen Kooi
2007-08-02 17:08 ` Michael Krelin
2007-08-02 22:16 ` Richard Purdie
2007-08-02 22:43 ` Michael Krelin
2007-08-03 8:04 ` Richard Purdie
2007-08-03 9:34 ` Michael Krelin
2007-08-05 11:29 ` Richard Purdie [this message]
2007-08-05 16:27 ` Michael Krelin
2007-08-05 20:21 ` Stanislav Brabec
2007-08-03 9:21 ` Stanislav Brabec
2007-08-05 11:32 ` Richard Purdie
2007-08-05 20:16 ` Stanislav Brabec
2007-08-05 20:27 ` Michael Krelin
2007-08-06 10:15 ` Stanislav Brabec
2007-08-06 16:28 ` Michael Krelin
2007-08-06 17:02 ` Stanislav Brabec
2007-08-05 5:55 ` Dr. Michael Lauer
2007-08-05 6:47 ` Mike (mwester)
2007-08-05 7:17 ` Dr. Michael Lauer
2007-08-02 12:56 ` Michael Krelin
2007-08-02 13:06 ` Koen Kooi
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=1186313341.5962.32.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.