From f34b1feaca557cd9da198610b67d4328fb0c7a84 Mon Sep 17 00:00:00 2001 From: Steffen Nurpmeso Date: Thu, 16 Feb 2017 15:49:02 +0100 Subject: -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(-) --- tccelf.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'tccelf.c') diff --git a/tccelf.c b/tccelf.c index ec92bdb..cc21325 100644 --- a/tccelf.c +++ b/tccelf.c @@ -1968,7 +1968,8 @@ static int elf_output_file(TCCState *s1, const char *filename) } if (s1->rpath) - put_dt(dynamic, DT_RPATH, put_elf_str(dynstr, s1->rpath)); + put_dt(dynamic, s1->enable_new_dtags ? DT_RUNPATH : DT_RPATH, + put_elf_str(dynstr, s1->rpath)); /* XXX: currently, since we do not handle PIC code, we must relocate the readonly segments */ -- cgit v1.3.1