diff options
| author | Steffen Nurpmeso <steffen@sdaoden.eu> | 2017-02-16 15:49:02 +0100 |
|---|---|---|
| committer | grischka <grischka> | 2017-02-18 09:54:41 +0100 |
| commit | f34b1feaca557cd9da198610b67d4328fb0c7a84 (patch) | |
| tree | aa74b09d8ff65b8b8429d149703f11abf4a8bb8f /tcc-doc.texi | |
| parent | 096125d963400951e0f160ced86416ef8c9c98b0 (diff) | |
| download | tinycc-f34b1feaca557cd9da198610b67d4328fb0c7a84.tar.gz tinycc-f34b1feaca557cd9da198610b67d4328fb0c7a84.tar.bz2 | |
-Wl, --enable-new-dtags for DT_RUNPATH instead of DT_RPATH
Today by accident i had to deal with linker problems of some
software and found an issue that mentioned DT_RUNPATH, which
mentioned that DT_RPATH is legacy and searched for
$LD_LIBRARY_PATH, whereas the newer DT_RUNPATH is searched
thereafter. Completely unencrypted! Well. For what's it worth,
i for one am astonished because of course i want to override
$LD_LIBRARY_PATH, but it surely has its merites, smart people came
to the conclusion, did they.
The attached diff below seems to be sufficient to support
DT_RUNPATH instead of DT_RPATH with tcc(1). But i have no insight
in what --enable-new-dtags is supposed to change in addition, so
i wonder.
Ciao!
--steffen
libtcc.c | 2 ++
tcc-doc.texi | 4 ++++
tcc.h | 1 +
tccelf.c | 3 ++-
4 files changed, 9 insertions(+), 1 deletion(-)
Diffstat (limited to 'tcc-doc.texi')
| -rw-r--r-- | tcc-doc.texi | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/tcc-doc.texi b/tcc-doc.texi index db1d28f..a1c6761 100644 --- a/tcc-doc.texi +++ b/tcc-doc.texi @@ -307,6 +307,10 @@ Generate an object file combining all input files. @item -Wl,-rpath=path Put custom search path for dynamic libraries into executable. +@item -Wl,--enable-new-dtags +When putting a custom search path for dynamic libraries into the executable, +create the new ELF dynamic tag DT_RUNPATH instead of the old legacy DT_RPATH. + @item -Wl,--oformat=fmt Use @var{fmt} as output format. The supported output formats are: @table @code |