I just tried out the new version of libtool and discovered that there was a change in the way the libtool script is generated. With previous versions (e.g. 1.5.8) the script was generated when you called AC_PROG_LIBTOOL, but with the new libtool version it seems to be generated when you call AC_OUTPUT.

The problem is that I have a configure test that uses libtool in order to check whether I can link against a shared library. The test I have written tests whether for a certain library a shared version is available. I need this test because I want to use that certain library in a shared library of my own and on some platforms you can't link a static version of a library to a shared library (because of PIC issues). To test this I just create a conftest.la library that references a symbol from the to-be-tested library and try to link with that library.

So my question is, is there still a way for me to perform my autoconf test now that the libtool script creation step is moved? Is it maybe possible to create the libtool script before AC_OUTPUT and still use my current test? Or are there other ways for me to test linking against a shared library, by e.g. using some combination of lt* variables that are available in the configure script to perform a compilation and link step?

Best regards,
Sander Niemeijer



_______________________________________________
Libtool mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/libtool

Reply via email to