This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: glibc's use of gnu_indirect_function feature - is it backwardscompatible?


On 8/16/2011 12:28 PM, Bryan Ischo wrote:
>> I would personally avoid linking statically.
>> 
>> Install the new libraries to /opt/sysroot/, and build your
>> applications with -Wl,--dynamic-linker=/opt/sysroot/lib/ld.so.1 and
>> the appropriate -Wl,-rpath=....
> 
> Thank you for the suggestion, and I appreciate the advice.  Just
> curious - what is the harm in static linking?  Larger memory
> footprint of the compiler, but I doubt that would even be noticed in
> this day and age of 12 GB development systems ...

(1) Eventually something calls dlopen and then you probably get the wrong runtime.

(2) Static linking isn't static if you access the network since NSS uses dlopen.

Cheers,
Carlos.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]