Andreas Metzler <[EMAIL PROTECTED]> wrote: > Basically the essence of the mess is #191425. If libfoo links against > libbar and application blah makes use of libfoo (but does not use > libbar) libtool will link the application against both libraries.
[...] O.k., understood. > Now libtool gets this information (libfoo links against libbar) from > the .la file, if you do not ship it, libtool cannot be that stupid and > link against all these dependcies. - The price you pay for that is > that _static_ linking does require following these dependency chains. Also o.k. > Personally I think the payoff is ok, due to dlopen in glibc (NSS, > iconv) static linking is unreliable anyway. This I don't understand. What is the relation between dlopen calls and static linking? For sure a statically linked binary won't use dlopen, and if it's a different one, what's the problem? TIA, Frank -- Frank Küster, Biozentrum der Univ. Basel Abt. Biophysikalische Chemie
