Re: libtool 1.4.1 tests

[Gary V. Vaughan]

On Sun, Sep 09, 2001 at 06:05:56PM +0100, s_a_white wrote:
> I've performed the following tests with the following results:

Cool!  Thanks.

> Now running configure detects the executable extension as none.   Performing
> a make builds the program but the link fails stating that log10 is an
> unresolved symbol.  Under 1.3.5 the code built fine, so am I supposed to
> hardcoding -lm now?

Nope.  That would be a bug :-(

> I now re-run the configure and it now detects the executable
> extension as .C ... !  I now build the code and it compiles fine so the
> maths library is already included.

!!  Do you know why that happens?

> I thought 1.4 was integrated with the multi-language branch and that had
> better support for c++?

Nope.  I merged the multi-language branch into the trunk after 1.4 was
released.  1.4b has the merged code, but there are still several warts.

> As for the extension detecting correctly I first
> reported this with libtool 1.3C.  libtool 1.3b had no problems and returned
> the extension correctly.

1.3b had its own code to detect EXEEXT, but this code was migrated to
autoconf and improved.  You might get further if you upgrade to a
newer autoconf... but 1.4 is still lacking multi-language support.

> I also hoped to update to 1.4 because I've had
> problems from some users by using libtool 1.3B and just hardcoding -lstdc++
> on the link line.

1.4 won't help much there I'm afraid... though it does fix many bugs
from 1.3b.

Cheers,
        Gary.
-- 
  ())_. Gary V. Vaughan     gary@(oranda.demon.co.uk|gnu.org)
  ( '/  Research Scientist  http://www.oranda.demon.co.uk       ,_())____
  / )=  GNU Hacker          http://www.gnu.org/software/libtool  \'      `&
`(_~)_  Tech' Author        http://sources.redhat.com/autobook   =`---d__/