Using libtool 2.0 in autoconf tests

[Sander Niemeijer]

Hi,

I have send this question to the list about a month ago, but 
unfortunately, there hasn't been an answer yet, and the release of 
libtool 2.0 is not that far away (right?).

<http://lists.gnu.org/archive/html/libtool/2004-10/msg00219.html>
<http://lists.gnu.org/archive/html/libtool/2004-10/msg00222.html>

I have some self written autoconf tests that check for linking shared 
libraries against some specific other libraries (these other libraries 
should be available as shared libraries or we might have a PIC problem. 
That is what my tests checks for). For this I had to create a variant 
of the AC_LINK_IFELSE macro that doesn't use CC/LD but the libtool 
script to perform the compilation/linking. With libtool 1.5.x the 
libtool script was nicely available, but with libtool 2.0 the libtool 
script is only available after AC_OUTPUT is handled. So _after_ all 
autoconf tests are performed.

How can I still perform my autoconf tests when libtool 2.0 comes out? 
Is there some way to generate the libtool 2.0 script before AC_OUTPUT? 
Is it otherwise possible to use some configure script variables in 
combination with ltmain.sh to perform my shared library specific 
AC_LINK_IFELSE check?

From a general perspective I also find it rather strange having the 
libtool script only available after AC_OUTPUT. It is like having CC (or 
any other necessary compiler/linker) only available after AC_OUTPUT. 
Since I am doing my compilation and linking with libtool, I would think 
it only logical that I would also be able to perform some autoconf 
tests with my compilation/linking tool.

Best regards,
Sander Niemeijer