On 01/06/2012 12:31 PM, Peter O'Gorman wrote:
On 01/06/2012 11:21 AM, Stepan Kasal wrote:
1) .la file always contains the recursively evaluated list of libraries.
While this is necessary for static linking and dumb dynamic linkers,
it is an issue for dyn. linkers that can do recursive resolutio
Russ Allbery writes:
> I don't believe this is correct. GNU/Linux does not add implicit
> dependencies at link time; it only links with the libraries that you
> explicitly list. ELF doesn't require that all symbols be resolved during
> the link, only the symbols in the thing that you're linking
Bob Friesenhahn writes:
> On Fri, 6 Jan 2012, Peter O'Gorman wrote:
>> This is still an issue, libtool always adds all dependencies. Many
>> packages assume this and don't explicitly add required dependencies to
>> Makefile.am etc. I don't recall the arguments for not changing this
>> when buildi
Hi,
I'm using libtool-2.4.2.
My package includes a dlopen'able module and a shareable library against
which it links. Here's the gist of the automake recipe:
#---
# exported support routines
lib_LTLIBRARIES = liblua_udunits2.la
These questions are quite common, and what they really come down to is that
many (or most) users want to solve a *different problem* than the one that
Libtool was designed to solve.
Libtool will deal with the platform specific vagaries of shared libraries
in a uniform manner. It isn't designed to
On Fri, 6 Jan 2012, Peter O'Gorman wrote:
This is still an issue, libtool always adds all dependencies. Many packages
assume this and don't explicitly add required dependencies to Makefile.am
etc. I don't recall the arguments for not changing this when building shared.
IIRC Scott tried to inc
On 01/06/2012 11:21 AM, Stepan Kasal wrote:
1) .la file always contains the recursively evaluated list of libraries.
While this is necessary for static linking and dumb dynamic linkers,
it is an issue for dyn. linkers that can do recursive resolution
(which is the case on GNU/Linux distributions
Hello,
I'm sad when I hear people rant about libtool, and I would like to
know the answers to that rants. The following bugs were, as I
supposed, known for years, but I may be wrong - perhaps they were
resolved years ago or they were never filed.
I would be very grateful if you could give me qui