Re: $max_cmd_len unset in libtool-1.5

[Peter O'Gorman]

Sam Steingold wrote:

> Specifically, the version of autoconf and automake should be irrelevant
> since the build process does not use them (the configure scripts are
> generated on a different host).  or maybe you are talking about the host
> where I generate configure?

I am talking about where you generate the package, so in this case cygwin, yes.

> build host (osx, as above):

> /usr/bin/libtool: Mach-O executable ppc

Hehe, love Apple's libtool :/, GNU libtool is known as glibtool on darwin 
(and similarly GNU libtoolize is glibtoolize).

> cygwin (where I generated the configure scripts):
>
> $ autoconf --version
> autoconf (GNU Autoconf) 2.59
> $ automake --version
> automake (GNU automake) 1.9.2
> $ libtool --version
> ltmain.sh (GNU libtool) 1.5.10 (1.1220.2.131 2004/09/19 12:46:56)

And these are all in the same prefix? And you still don't get max_cmd_len?

In what will be libtool-2.0 libtool will complain if ltmain.sh and 
libtool.m4 versions are mismatched, but there is no such feature in the 1.5 
branch.

Peter
--
Peter O'Gorman - http://www.pogma.com