How do absolute paths get into the `NEEDED` portion of the dynamic section of an executable?

Asked Apr 12 '15 at 20:35

Active Dec 15 '21 at 18:10

Viewed 842 times

I have a number of executables which link against a single lib path. For instance, the executable foo links against (say) libboost_system.so and libfoo.so, the latter of which I build myself. I place third party libraries in a variable LDLIBS, and link my library via -lfoo, so that the makefile line looks as follows:

foo: objects
    $(CXX) $(LDFLAGS) -o $@ $^ $(LDLIBS) -lfoo

However, when I readelf, I see my own path!

$ readelf --dynamic foo 

Dynamic section at offset 0x3c68 contains 48 entries:
  Tag        Type                         Name/Value
 0x0000000000000001 (NEEDED)             Shared library: [/home/username/foo_dir/lib/libfoo.so]
 0x0000000000000001 (NEEDED)             Shared library: [libboost_system.so.1.58.0]

My own library is the only library which has an absolute path in it.

How can I get rid of this monstrosity using only the makefile, i.e., without using patchelf --replace-needed or chrpath?

edited Dec 15 '21 at 18:10

asked Apr 12 '15 at 20:35

user14717

4,757
2
44
68

Did you add `-L/home/nthompson/foo_dir/lib/` when linking? – StenSoft Apr 13 '15 at 12:12
Yes; it links just fine. – user14717 Apr 13 '15 at 12:30
If there is no absolute path, where do you expect the dynamic loader to find it? – paq Jul 17 '15 at 14:07
1

Using the `ORIGIN` variable in the executable. – user14717 Jul 17 '15 at 14:16

How do absolute paths get into the `NEEDED` portion of the dynamic section of an executable?

0 Answers0