All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: invalid removal of rpath from native binaries during installation or staging
Date: Fri, 02 Jul 2010 13:52:53 +0100	[thread overview]
Message-ID: <1278075173.30247.531.camel@rex> (raw)
In-Reply-To: <1278026396.8213.51.camel@utx.utx.cz>

On Fri, 2010-07-02 at 01:19 +0200, Stanislav Brabec wrote:
> Tom Rini wrote:
> 
> > Can you use readelf -d on your perl?  The whole point of the relative 
> > path calculation that relocatable.bbclass does is to fix the hard cases 
> > like perl.   Thanks!
> > 
> 
> I found the problem:
> 
> The runtime expansion of $ORIGIN works only if /proc is mounted!
> 
> My build environment is a minimal openSUSE 11.2 x86_64 subset inside
> chroot with no /proc, /sys, and /dev with null zero and few other static
> items.
> 
> Not having /proc is an advantage in most cases (cross configure cannot
> check host system), but breaks in this case.
> 
> Maybe it would be nice to allow to configure to not inherit relocatable
> in native.bbclass for people who don't want to mount /proc.

As we try to improve staging, we're going to be working on the
assumption all packages are relocatable. If we allow disabling of this
it will break various assumptions in the code. I'd therefore suggest
you're free to do this locally but it shouldn't be an easily available
option. Building without /proc mounted is a rather specialist usecase. 

If it really worries you, mount /proc somewhere else and symlink the
bare minimum needed.

Cheers,

Richard




      reply	other threads:[~2010-07-02 12:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01 22:05 invalid removal of rpath from native binaries during installation or staging Stanislav Brabec
2010-07-01 22:41 ` Tom Rini
2010-07-01 23:19   ` Stanislav Brabec
2010-07-02 12:52     ` Richard Purdie [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=1278075173.30247.531.camel@rex \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@lists.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.