Hi Andreas,
[[adding Cc: bug-autoconf]]
Thanks for testing libtool, and for the report.
On 11 Jun 2010, at 05:02, Andreas Schwab wrote:
> 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.
Looks like a bug in autoconf. If there is no working C++ compiler, AC_PROG_CXX
ought not to pretend that there is.
> # -*- compilation -*-
> 21. flags.at:24: testing ...
> ./flags.at:24: { test -n "$CXX" && test "X$CXX" != Xno; } || (exit 77)
> enable shared libraries
Odd. Just below that line in my copy of tests/testsuite it says:
test "X$CXX" != Xg++ || (g++ -v >/dev/null 2>&1) || (exit 77)
...which really should skip the test if `g++ -v' doesn't work. :(
Can you investigate why that exit isn't firing on your setup?
> ./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)
Cheers,
--
Gary V. Vaughan (g...@gnu.org)
