Todd Fleming wrote:
>> That is _not_ the generated one from the configure process. The
>> Makefile will execute a libtool script in the top build directory.
> I'm having trouble with so many packages I decided to reproduce the
> problem independant of any of them, thus the foo.c example. Once I know
> I have a working libtool somewhere then I can go about replacing the
> broken ones that came with the packages I'm trying to build.
> I was hoping that the libtool that with came with msys could somehow
> work, but it exhibits the same behavior as the ones that come with other
Sorry, I've only used libtool from autotools that others have already
configured. I'll play with it, and see what I can do. I'll upgrade to
the latest CVS to see if that helps any.
>> So what is it you're trying to build? You must be in the top source
>> directory to execute the autoreconf process.
> A ton of packages I've downloaded. The libtool versions that come with
> the overwelming majority of packages I've downloaded from various
> sources are broken.
Yes, I know, it's a mess. IMO, the whole of autotools could use a
rewrite beginning with the design phase. There are various projects
that are trying to do that. What I think I'll do for libtool and MinGW
is to create a minlibtool that only works for MinGW and I'll suggest
that the generated libtool scripts be replaced with the libtool from
I do understand your frustration.
> Here's one I'm strugling with right now: gtk+-2.2.4 (libtool 1.5).
> libtool incorrectly creates static libs for some of the components and
> dlls from others. When it tries to link the dlls that rely on the
> incorrectly built static libs, it complains loudly that static libs
> can't be linked into dlls (this of course is not true on Win32). I've
> had to build most packages I download by hand because libtool keeps
> regressing to static builds.
>> From what I've been able to find, libtool 1.5 is the most recent. Do you
> know of an older one that works? Is there a special libtool version that
> has been patched for msys somewhere? If so, I'll replace the one that
> comes with the packages I'm trying to build.
You're already using it. For whatever reason, libtool isn't picking up
on the fact that you want a shared library. I modified your link
command above to ``libtool --mode=link gcc -shared -o foo.dll foo.lo''
and viola I get a foo.dll.exe file, which is a shared library with the
> BTW, this is definately *not* a MingW or msys-only problem. The same
> thing happens under Cygwin. I'm posting here because I prefer to get a
> working build using msys rather than Cygnus.
I think the problem extends beyond Windows platforms. I monitor the
autotools lists and I know that the archives are full of problems from