On Thu, 2010-04-01 at 11:33 -0700, Tom Rini wrote: > On Thu, 2010-04-01 at 19:09 +0100, Richard Purdie wrote: > > On Thu, 2010-04-01 at 09:45 -0700, Tom Rini wrote: > > > There's two uglies here. Ugly one, above. Quoting isn't nice to read > > > and gdb/gcc/binutils are special. It does however, work from the > > > get-go. And the only cases it doesn't get right, right off the bat are > > > some perl (and possibly python) module cases where we aren't giving the > > > right relative path there, but we can always figure it out and fix that > > > up per recipe. Ugly two, the chrpath way. Depends on having a big > > > enough RPATH in the initial binary to patch over. Doesn't work if the > > > RPATH isn't long enough as you say, which is why you can't do it on > > > -cross. > > > > I've done the maths and it will always work within the sysroots/staging > > directory as there is always enough length available. Since we want rid > > of /cross/ for various reasons anyway I don't think this is a reason > > against this approach. > > What do you want to do on nativesdk ? That's where this gets real > important as well.
I'd argue for the same approach. We'd just have to ensure the base path used for the SDK is long enough to accommodate this but again, thats not difficult to arrange. Cheers, Richard _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
