Bob Friesenhahn <[EMAIL PROTECTED]> writes: > Quite a lot can known from .la files but it is apparent that .la files > are now spontaneously deleted.
Hm, I must admit that I generally find them useless compared to reading readelf -a output, but I'm not the normal user. :) > It is really quite a burden on the developer to try to understand what > is needed for static and shared linking. Many Linux application/library > authors are not even aware of all the libraries they are using and it > might not be possible to fully know without using diagnostic tools, > special environment variables like LD_BIND_NOW, or a particular > execution mode of the software. Dependencies are not always obvious and > is is possible for "pass through" dependencies to be introduced > (stealthy hard dependencies) that the developer is not aware of. This is all true in the general case, but most of the cases where clients of a library need to link against that library's dependencies are weird edge cases. My guess is that only linking with the libraries whose ABIs you call directly works 95% of the time on modern ELF platforms, and linking with -pthread where appropriate is the only additional bit required in another 4% or more of the cases. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
