[Bug ld/20159] Dynamic Linking Change for Shared Libraries (1.24 to 1.26)

[paul.braman at nielsen dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=20159

--- Comment #9 from Paul Braman <paul.braman at nielsen dot com> ---
HJ, maybe you might be on to something ...

I took the test case and compiled it clean on both machines. If I use the
executable I created on Ubuntu 14.04, the test case runs as expected regardless
of which shared library it is running against and regardless of which VM I am
running it on. The reverse (executable built on 16.04) is also true (fails
regardless of library/VM).

[Someone might want to double check my work.]

address@hidden:linkertest] gcc -fPIC -c -I. -o nothing.lo nothing.c
address@hidden:linkertest] gcc -shared -rdynamic -o libnothing.so
nothing.lo
address@hidden:linkertest] gcc -o something something.c faketime.c
-Wl,-rpath=. -L. -lnothing
address@hidden:linkertest] ./something
42
42
address@hidden:linkertest] md5sum something
1f2e26a68c8e7576fafda6aa0e947490  something
address@hidden:linkertest] scp
address@hidden:test/linkertest/something ./
address@hidden's password:
something                                                                      
                      100% 8704     8.5KB/s   00:00
address@hidden:linkertest] md5sum something
3464ea630b6a075e6adf9b15aaf3412f  something
address@hidden:linkertest] ./something
42
1464701962
address@hidden:linkertest]

This is just one of the example cases. I also moved the library built from
14.04 to 16.04 and then compiled the executable and ran it (and visa versa).

Dynamic linking, itself, does not seem to be the culprit. I'm not sure where
the problem lies now (GCC, glibc, or ld).

-- 
You are receiving this mail because:
You are on the CC list for the bug.