gcc

[Michael Schwendt]

On Sun, 04 Jul 2004 14:46:54 +0200, Alexander Dalloz wrote:

> Am So, den 04.07.2004 schrieb ricardo um 3:14:
> 
> > hi I have some probles to compile kmerlin-0.3.1
> > 
> > [root at dc86d8776 kmerlin-0.3.1]#  ./configure
> > loading cache ./config.cache
> > checking host system type... i686-pc-linux-gnuoldld
> > checking target system type... i686-pc-linux-gnuoldld
> > checking build system type... i686-pc-linux-gnuoldld
> > checking for a BSD compatible install... /usr/bin/install -c
> > checking for -p flag to install... yes
> > checking whether build environment is sane... yes
> > checking whether make sets ${MAKE}... 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 a C-Compiler...
> > checking for gcc... gcc
> > checking whether the C compiler (gcc  ) works... no
> > configure: error: installation or configuration problem: C compiler cannot create executables.
> > [root at dc86d8776 kmerlin-0.3.1]#
> 
> Install a complete development environment. See the above lines with
> missing, they indicate that you are missing important packages like
> autoconf. It is no gcc problem.

It is.

> checking whether the C compiler (gcc  ) works... no
> configure: error: installation or configuration problem:
> C compiler cannot create executables.

This can be due to anything ranging from a missing/incompatible binutils
package to other sorts of damage in the compiler suite. Above check tries
to build and run a simple test program. What does config.log in the build
directory say?