bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/2676] New: ld and shared libraries


From: Philippe dot Vouters at laposte dot net
Subject: [Bug binutils/2676] New: ld and shared libraries
Date: 20 May 2006 10:33:11 -0000

I noticed that, instead of inserting a soft shared library link inside the
executable, Linux linker (ld) inserts the resolved shared library name. This
forces programs to be relinked each time an actual shared library name has
changed, after any upgrade either using yum or distribution upgrades. This
prevents me from using programs which are shipped within an RPM and are linked
under FC4, such as Openwengoo among some. Providing ldd would show a soft link,
this would enable to more easily distribute executable programs.

HP Unices (HP-UX and Tru64) linkers only inserts in the programs the soft link,
enabling to easily install library patches with a different extension without
having to relink all programs.

So I'd like to report this wish to ld and dl (dynamic loader) maintainers so
that soft shared libraries links are used instead.

Reproducer:

address@hidden ~]$ cat hello.c
#include <stdio.h>
int main(){
printf("Hello!\n");
return 1;
}
address@hidden ~]$ cc -c  hello.c
address@hidden ~]$ cc -o hello -lc hello.o
address@hidden ~]$ ldd hello
        linux-gate.so.1 =>  (0x00a1b000)
        libc.so.6 => /lib/libc.so.6 (0x001a6000)
        /lib/ld-linux.so.2 (0x0018b000)

-- 
           Summary: ld and shared libraries
           Product: binutils
           Version: unspecified
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: binutils
        AssignedTo: unassigned at sources dot redhat dot com
        ReportedBy: Philippe dot Vouters at laposte dot net
                CC: Philippe dot Vouters at laposte dot net,bug-binutils at
                    gnu dot org


http://sourceware.org/bugzilla/show_bug.cgi?id=2676

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]