Re: Build failure (libsupc++)

[Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>]

* Bruce Korb wrote on Sat, Jun 07, 2008 at 11:11:54PM CEST:
> $ bash  ../gcc/configure --disable-multilib --prefix=/home/gnu/proj/gcc-inst --enable-languages=c,c++ --enable-bootstrap 
> [...]
> $ make
> [...]
> Making all in libsupc++
> make[4]: Entering directory `/home/gnu/proj/gcc-bld/x86_64-unknown-linux-gnu/libstdc++-v3/libsupc++'
> /bin/sh ../libtool --tag CXX --tag disable-shared --mode=compile /home/gnu/proj/gcc-bld/./gcc/xgcc -shared-libgcc -B/home/gnu/proj/gcc-bld/./gcc -nostdinc++ -L/home/gnu/proj/gcc-bld/x86_64-unknown-linux-gnu/libstdc++-v3/src -L/home/gnu/proj/gcc-bld/x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs -B/home/gnu/proj/gcc-inst/x86_64-unknown-linux-gnu/bin/ -B/home/gnu/proj/gcc-inst/x86_64-unknown-linux-gnu/lib/ -isystem /home/gnu/proj/gcc-inst/x86_64-unknown-linux-gnu/include -isystem /home/gnu/proj/gcc-inst/x86_64-unknown-linux-gnu/sys-include -I/home/gnu/proj/gcc/libstdc++-v3/../gcc -I/home/gnu/proj/gcc-bld/x86_64-unknown-linux-gnu/libstdc++-v3/include/x86_64-unknown-linux-gnu -I/home/gnu/proj/gcc-bld/x86_64-unknown-linux-gnu/libstdc++-v3/include -I/home/gnu/proj/gcc/libstdc++-v3/libsupc++  -fno-implicit-templates -prefer-pic -Wall -Wextra -Wwrite-strings -Wcast-qual  -fdiagnostics-show-location=once  -ffunction-sections -fdata-sections  -g -O2   -D_GNU_SOURCE    -c -o array_type_info.lo ../../../../gcc/libstdc++-v3/libsupc++/array_type_info.cc
> ../libtool: line 811: X--mode=compile: command not found
> ../libtool: line 978: *** Warning: inferring the mode of operation is deprecated.: command not found
> ../libtool: line 979: *** Future versions of Libtool will require --mode=MODE be specified.: command not found
> ../libtool: line 1122: X/home/gnu/proj/gcc-bld/./gcc/xgcc: No such file or directory
> ../libtool: line 1122: X-shared-libgcc: command not found

Somehow your tree ended up with inconsistent ltmain.sh vs. libtool.m4,
one from 1.5.x and one from the 1.9 tree or newer.  I haven't checked
whether somebody committed broken files like this today, but they were
ok Saturday morning.  Have you used --enable-maintainer-mode on the
tree?

Cheers,
Ralf