Why doesn't configure use libtool during its test links?
Howdy. Perhaps I'm missing something obvious, but it seems to me there's a fundamental flaw in the libtool/autoconf integration (described as "seamless" in the info docs). I'm using libtool to allow my package to link with 3rd-party shared libraries (that aren't in /usr/lib or the default shared library search path). Everything is set up nicely so that the eventual link of the main executable will use libtool, but the test links done by configure _don't_ use it! I guess I can write custom autoconf tests that use libtool when linking, rather than using the predefined macros, but this seems kind of needless. Shouldn't AM_PROG_LIBTOOL cause configure to use libtool during all its test links? -- Dan Harkless SpeedGate Communications, Inc. ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Re: Why doesn't configure use libtool during its test links?
On Mar 27, 2001, "Dan Harkless" <[EMAIL PROTECTED]> wrote:
> Everything is set up nicely so that the eventual link of the main
> executable will use libtool, but the test links done by configure
> _don't_ use it!
> Shouldn't AM_PROG_LIBTOOL cause configure to use libtool during all
> its test links?
Yep. It's been in my to-do list for ages.
The main stumbling block is that libtool currently requires separate
compile and link phases, whereas autoconf assumes it is possible to
compile-and-link with a single command.
Contributions would be very welcome.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
