static blending/relinking

[Nesius, Robert]

There's no reason your software can't be portable using shared libraries
if you use 'embedded paths' during your links so that your binaries use
YOUR libraries.  That would mean sending flags like
'-Wl,-rpath,/path/to/my/libs/that/is/not/in/ld.so.conf' or something
like that.  You can do this on linux, HPUX, AIX, Solaris, and more. It
also means you should bundle up your shared libs along with your apps so
that you are not at the mercey of the flavor of the operating system you
are on.  

-Rob
 

-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
Behalf Of porte64@free.fr
Sent: Friday, March 26, 2004 4:42 AM
To: gcc-help@gcc.gnu.org
Subject: static blending/relinking

Does gcc's linker provide options to generate a static binary from ELF
pieces (executable + dynamically-linked libraries) ?

If someone would be kind enough to give a command line sample ...

Someone wrote such an ELF swiss-knife: reducebind.c but it is alpha and
only works on Linux.
It's able to only take the needed parts of code within each library,
which is great.
Can gcc's linker behave so ?

Anyway the need of such a software engineering tool is real, e.g. for
all those who want to design busyboxes, make commercial software
portable, etc ... Essential.

Best regards
Paul