On Sat, 13 Jan 2001 18:42:08 -0800 (PST), Tib said:
> Ok - here's how it all begins:
>
> I'm trying to compile a program - so I run ./configure and get the following
> results:
>
> [root@unica linux]# ./configure
> loading cache ./config.cache
> checking for a BSD compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... yes
> checking for working aclocal... missing
> checking for working autoconf... found
> checking for working automake... missing
> checking for working autoheader... found
> checking for working makeinfo... missing
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for gcc... gcc
> checking whether the C compiler (gcc ) works... yes
> checking whether the C compiler (gcc ) is a cross-compiler... no
> checking whether we are using GNU C... yes
> checking whether gcc accepts -g... yes
> checking for c++... no
> checking for g++... no
> checking for gcc... gcc
> checking whether the C++ compiler (gcc ) works... no
> configure: error: installation or configuration problem: C++ compiler cannot
> create executables.
>
>
> I thought this would be fixable by installing a new compiler (or updating, at
> least). So I get new packages for gcc (2.95-12 and c++2.95-12 packages of
> gcc) and both fail when I try to run an upgrade (rpm -Uvh) of a failed
> dependency on /usr/sbin/update-alternatives. If I'm taking the hard route, can
> someone bap me upside the head please?
>
> <EOL>
> Tib
Even tho the upgrade of rpm is a collateral issue, it's one you should go ahead
& address. You need to be at least at the 3.0.5-x level anyway to avoid rpm
version issues.
