Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Joshua Lock : relocatable: Class to post-process packages for relocatability
Date: Fri, 02 Apr 2010 22:23:35 +0100	[thread overview]
Message-ID: <1270243415.4993.173.camel@rex> (raw)
In-Reply-To: <hp471c$59h$1@dough.gmane.org>

On Fri, 2010-04-02 at 09:40 +0200, Koen Kooi wrote:
> On 02-04-10 00:07, Tom Rini wrote:
> > On Thu, 2010-04-01 at 13:44 +0000, git version control wrote:
> >> +def rpath_replace (path, d):
> >> +    bindirs = bb.data.expand("${bindir} ${sbindir} ${base_sbindir} ${base_bindir} ${libdir} ${base_libdir} ${PREPROCESS_RELOCATE_DIRS}", d).split()
> > 
> > Is that last variable there to let recipes add non-standard locations to
> > the search path?

Yes, as long as all users append to it, it will work like that and that
use makes sense.

> > [snip]
> >> -       required_utilities = "patch help2man diffstat texi2html
> > makeinfo cvs svn bzip2 tar gzip gawk md5sum"
> >> +       required_utilities = "patch help2man diffstat texi2html
> > makeinfo cvs svn bzip2 tar gzip gawk md5sum chrpath"
> > 
> > How hard would it be to add a chrpath-native recipe and maybe treat this
> > like we used to treat qemu?  Don't see it in yum on my rhel5 box.
> > Thanks.
> 
> We already have that from our previous chrpath experiments :) See
> recipes/chrpath

As does Poky. The tricky bit isn't the recipes, its the dependencies and
making sure we don't end up with any binaries that haven't had the
relocation treatment.

Cheers,

Richard




  parent reply	other threads:[~2010-04-02 21:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1NxKhE-0007AO-Bh@melo.openembedded.org>
2010-04-01 22:07 ` [oe-commits] Joshua Lock : relocatable: Class to post-process packages for relocatability Tom Rini
2010-04-02  7:40   ` Koen Kooi
2010-04-02 16:26     ` Tom Rini
2010-05-03 23:49       ` Tom Rini
2010-04-02 21:23     ` Richard Purdie [this message]
2010-04-02 22:33       ` Tom Rini

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=1270243415.4993.173.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox