openembedded-core.git/meta/classes/chrpath.bbclass, branch fido

chrpath.bbclass: handle RUNPATH as well as RPATH

2015-03-16T17:38:35+00:00

Binaries linked with gold may contain a RUNPATH instead of an RPATH.
Update chrpath.bbclass process_file_linux() to handle both cases.

Signed-off-by: Andre McCurdy 
Signed-off-by: Ross Burton

chrpath: Drop warning from darwn builds

2014-08-17T09:01:30+00:00

This was old debug which can safely be removed for less noisy builds.

Signed-off-by: Richard Purdie

chrpath: properly handle rootdir with '..' in path

2014-05-11T11:24:21+00:00

When there is a '..' in the rootdir path, rootdir will not be a substring of
fpath.  This causes an incorrect rpath of the difference between the workdir
and the sysroot to be computed, which is incorrect.  Normalizing basedir
fixes this issue.

Signed-off-by: Richard Purdie

chrpath: Improve crazy code

2013-11-27T12:03:18+00:00

The current code is a little bit overcomplicated, deficient and also
possibly broken.

Issues include:

a) Not maximally optisming rpaths (e.g. a lib in usr/lib might get an
   rpath of $ORIGIN/../../usr/lib)
b) The return in the middle of the for loop look suspiciously like
   it might break on some binaries
c) The depth function, loops of "../" prepending and so on can
   be replaced with a call to os.path.relpath

This patch cleans up the above issues.

Running binaries should result in less "../" resolutions which can't
hurt performance either.

[YOCTO #3989]

Signed-off-by: Richard Purdie

chrpath: Add support for relocating darwin binaries

2013-08-22T17:30:07+00:00

On darwin, install_name_tool can be used to relocate binaries/libraries. This
adds support for adjusting them with relative paths rather than hardcoded ones.
The Linux code is factored out into a function but is otherwise unchanged.

Signed-off-by: Richard Purdie

chrpath.bbclass: Normalize rpath only of it doesn't contain ORIGIN variable

2012-12-14T08:50:06+00:00

If we normalize a rpath which contains ORIGIN variable, the binary will end
up without those rpaths at all. So check first if rpath contains ORIGIN variable
and if not, move on and normalize it.

Signed-off-by: Andrei Gherzan 
Signed-off-by: Richard Purdie

chrpath: normalize the paths

2012-12-13T15:27:38+00:00

By normalizing the paths the path comparing code works correct
to generate the right RPATH even when there is a A/../A in TMPDIR

[YOCTO #3408]

Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

chrpath.bbclass: Account for case when ORIGIN is in RPATH

2012-08-17T16:44:57+00:00

This fixes a case when RPATH embedded in program have one of
its path already relative to ORIGIN. We were losing that path
if such a path existed. This patch appends it to the new edited
rpath being created when we see it.

so RPATH like below

(RPATH)              Library rpath:
[$ORIGIN/../lib/amd64/jli:$ORIGIN/../jre/lib/amd64/jli]

would end up being empty

but after this patch its kept intact

Signed-off-by: Khem Raj 
Signed-off-by: Richard Purdie

chrpath.bbclass: Ensure we only process tmpdir in paths which actually contain that path

2012-08-17T16:42:37+00:00

Without this change, a path to "/lib/xxx" or "/usr/lib/xxx" would also
attempt to be remapped to be relative to $ORIGIN which makes no sense.

Signed-off-by: Richard Purdie

classes/chrpath: improve chrpath failure handling

2012-08-17T14:25:01+00:00

When chrpath fails, prefix the error message with the name of the recipe
that is being processed, and include the the output from chrpath, as
well as making the calling task actually fail.

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie