On Tue, Apr 23, 2002 at 01:13:01AM -0400, Andy Blyler wrote:
Great! That fixed that issue. How it says that my C++ compiler is
non existant.
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking for gcc... (cached) gcc
checking whether the C compiler (gcc -L/usr/lib) works... yes
checking whether the C compiler (gcc -L/usr/lib) is a
cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking how to run the C preprocessor... (cached) gcc -E
checking for AIX... no
checking for minix/config.h... no
checking for gawk... (cached) gawk
checking for c++... no
checking for g++... no
checking for gcc... gcc
checking whether the C++ compiler (gcc -L/usr/lib) works... no
configure: error: installation or configuration problem: C++ compiler
cannot cre
ate executables.
configure: error: ./configure failed for bdbobj
Look in the config.log file in the build directory. It often has
the clue necessary to figure out what's happening.
Bill
``One of the common failings among honorable people is a failure to
appreciate how thoroughly dishonorable some other people can be, and how
dangerous it is to trust them.''
- Thomas Sowell