[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [libtool 2.2.10] testsuite: 21 102 failed
From: |
Ralf Wildenhues |
Subject: |
Re: [libtool 2.2.10] testsuite: 21 102 failed |
Date: |
Fri, 11 Jun 2010 06:01:43 +0200 |
User-agent: |
Mutt/1.5.20 (2009-10-28) |
Hello Andreas,
thanks for the bug report.
* Andreas Schwab wrote on Fri, Jun 11, 2010 at 12:02:20AM CEST:
> There is no C++ compiler anywhere.
>
> [...]
> checking for g++... no
> [...]
> checking whether g++ accepts -g... no
> [...]
>
> In the AC_PROG_CXX macro AC_CHECK_TOOLS is called with [g++] as
> value-if-not-found.
Yep, known issue in Autoconf.
> 21. flags.at:24: testing ...
> ./flags.at:24: { test -n "$CXX" && test "X$CXX" != Xno; } || (exit 77)
> enable shared libraries
> ./flags.at:24: $LIBTOOL --tag=CXX --mode=compile $compile -c $source
> stderr:
> /usr/src/packages/BUILD/libtool-2.2.10/libtool: line 1159: g++: command not
> found
> stdout:
> libtool: compile: g++ -c a.cpp -o .libs/a.o
> ./flags.at:24: exit code was 1, expected 0
> 21. flags.at:24: 21. passing CXX flags through libtool (flags.at:24): FAILED
> (flags.at:24)
This should have been fixed already as a side effect of
v2.2.10-3-g8f241f6, 'Factorize testing gcj installation in the
testsuite.'
Cheers,
Ralf