/lib/cpp again

[Ralf Corsepius]

Hi,

the tarball below demonstrates a couple of problems with autotools :

Environment: Linux, autoconf-cvs, automake-cvs (Both as of Monday
this week), libtool-1.4, gcc-3.0.1 installed to /opt/gcc30.

./configure 
..
checking for g++... g++
checking for C++ compiler default output... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix... 
checking for object suffix... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C++ preprocessor... g++ -E
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking how to run the C preprocessor... /lib/cpp
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking dependency style of gcc... gcc3
checking for ld used by GCC... /opt/gcc30/bin/ld
checking if the linker (/opt/gcc30/bin/ld) is GNU ld... yes
checking for /opt/gcc30/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /opt/gcc30/bin/nm -B
..

Note the "how to run the C preprocessor .. /lib/cpp".

This is the wrong cpp, because I am not using the system's primary
toolchain installed to /usr, but a secondary toolchain installed to
/opt/gcc30.
(PATH=/opt/gnu30/bin:...) with /opt/gcc30/bin/cpp and
/opt/gcc30/bin/gcc being present.

I am not sure what actually causes this problem (Using libtool w/
c++? Dependency tracking? Bug in autoconf?) :) To avoid
cross-posting, I am posting to address@hidden only :)

Ralf

hello-test.tar.bz2
Description: Binary data