Re: Packaged-staging and RPATH with native/cross/sdk

[Tom Rini <trini@embeddedalley.com>]

On Thu, Jul 30, 2009 at 03:16:58PM -0700, Chris Larson wrote:

> I've been using a $ORIGIN rpath in my builds, and it's definitely a
> step in the right direction.  Iirc there are a few quirks with things
> like perl modules and such, but you can work around those.
> 
> There are a lot of relocation issues with stuff we stage that need to
> be fixed one by one to use those particular staging packages with tmp
> in a different location, though.  Sadly, few upstream packages are
> really relocatable.  Some of it can be worked around by exporting env
> vars.. for example, you can point 'file' at its data with an env var,
> and you can override nearly all the paths used in autoconf/automake
> via env vars (the autotools branch i started work on does that).

Perhaps we need to whitelist some cross/native/sdk packages?  What
people really notice is building gcc a few times, and that stuff is
relocatible (and if these aren't, it's a recipe bug).  Might be a few
others too, but just not rebuilding gcc will be noticed.

-- 
Tom Rini