Doug Morris <[EMAIL PROTECTED]> writes:
> Ruud de Rooij wrote:
> >The current CVS version uses libtool if available. However, the libtool
> >that comes with my Linux distribution (Debian GNU/Linux "potato", GNU
> >libtool 1.3.3) doesn't understand the -static option and the compile fails.
> >Maybe the check for libtool should be made somewhat more intelligent?
>
> Damn, you're fast. I just committed that.
Hehe :-)
> I was going to put up a tar
> file after I finished a few more things and ask people to test. There
> isn't a libtool on my RedHat system, or on Solaris, OpenBSD or SunOS.
> I thought it was an Apple thing.
It's apparently also a GNU thing. I don't think Apple libtool and GNU
libtool have the same purpose, though (maybe they once did but
diverged).
> The easiest fix is to say "when on Rhapsody do this" but I'm trying to
> wean nmh from the CANONICAL_SYSTEM stuff, which means. I guess I can
> try to write a custom test for ranlib and fail to libtool only if
> ranlib is broken. Except the ranlib on the mac isn't totally broken...
> I'll see what I can figure out.
Another way to approach it is to check if libtool supports a "-static"
option and don't use it if it isn't supported. Let me know if you
need more info.
I also found that there was no way to tell configure to skip the
libtool check. It accepts an absolute path in the LIBTOOL environment
variable, but no way to disable it (setting LIBTOOL to "no" doesn't
work).
> Or is libtool preferred on Debian, but with different options?
It's available as an optional package and some packages indeed use it
in their build process, but it's certainly not the preferred or
standard way to build libraries.
- Ruud de Rooij.
--
ruud de rooij | [EMAIL PROTECTED] | http://ruud.org
