]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.git/commit
bitbake.conf: add --enable-new-dtags to linker
authorAlexander Kanavin <alex.kanavin@gmail.com>
Fri, 21 Dec 2018 14:23:51 +0000 (15:23 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Fri, 11 Jan 2019 10:39:08 +0000 (10:39 +0000)
commit69a4542fc4a3ea83b86940a791bb6c82fb35ce7a
tree778fd4201357b2c7f20b7dcd2ec852f35d80c84d
parentc3a244b792ca89f28048c1fec1d3e05112872ee0
bitbake.conf: add --enable-new-dtags to linker

Various versions of ld have different defaults for this
(even between e.g. Ubuntu 16.04 and 18.04). This has the
consequence of putting either RPATH or RUNPATH into the binary,
depending on the linker, which have different priorities
vs LD_LIBRARY_PATH env var. Also, I think, the original
executable binary is looked up for the tags when resolving
a dependency of a shared library when using RPATH, but not
RUNPATH.

Let's make this deterministic.

(From OE-Core rev: 661d700ab7428b0ad982bfd2714cca134bad85a2)

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/conf/bitbake.conf