autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: checking for C compiler default output...


From: vincent blondel
Subject: Re: checking for C compiler default output...
Date: Thu, 12 Sep 2002 21:29:10 +0200

I give you here the content of my config.log

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by configure, which was
generated by GNU Autoconf 2.52.  Invocation command line was

  $ ./configure

## ---------- ##
## Platform.  ##
## ---------- ##

hostname = PINGUIN
uname -m = i686
uname -r = 2.4.18-8.1mdk
uname -s = Linux
uname -v = #1 Mon Jun 24 13:21:53 MDT 2002

/usr/bin/uname -p = unknown
/bin/uname -X     = unknown

/bin/arch              = i686
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
hostinfo               = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH =
/opt/kde3/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/games:/usr/li
b/jre-1.3.1_02/bin:/home/jlang/bin

## ------------ ##
## Core tests.  ##
## ------------ ##

configure:978: PATH=".;."; conftest.sh
./configure: conftest.sh: command not found
configure:981: $? = 127
configure:1024: checking build system type
configure:1042: result: i686-pc-linux-gnu
configure:1049: checking host system type
configure:1063: result: i686-pc-linux-gnu
configure:1070: checking target system type
configure:1084: result: i686-pc-linux-gnu
configure:1158: checking for gcc
configure:1173: found /usr/bin/gcc
configure:1181: result: gcc
configure:1409: checking for C compiler version
configure:1412: gcc --version </dev/null >&5
2.96
configure:1415: $? = 0
configure:1417: gcc -v </dev/null >&5
Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux-gnu/2.96/specs
gcc version 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)
configure:1420: $? = 0
configure:1422: gcc -V </dev/null >&5
gcc: argument to `-V' is missing
configure:1425: $? = 1
configure:1445: checking for C compiler default output
configure:1448: gcc    conftest.c  >&5
gcc: installation problem, cannot exec `cpp0': No such file or directory
configure:1451: $? = 1
configure: failed program was:
#line 1429 "configure"
#include "confdefs.h"

int
main ()
{

  ;
  return 0;
}
configure:1474: error: C compiler cannot create executables

## ----------------- ##
## Cache variables.  ##
## ----------------- ##

ac_cv_build=i686-pc-linux-gnu
ac_cv_build_alias=i686-pc-linux
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_host=i686-pc-linux-gnu
ac_cv_host_alias=i686-pc-linux
ac_cv_prog_ac_ct_CC=gcc
ac_cv_target=i686-pc-linux-gnu
ac_cv_target_alias=i686-pc-linux


configure: exit 77

----- Original Message -----
From: "Lars Hecking" <address@hidden>
To: <address@hidden>
Sent: Thursday, September 12, 2002 7:35 PM
Subject: Re: checking for C compiler default output...


> vincent blondel writes:
> > Hi all,
> >
> > I am trying to compile all packages for a Linux from Scratch
installation
> > but I encounter problem with the compilation.
> > I am using Mandrake 8.2 on a AMD Athlon Xp1600+ and I got following
> > messages.
> >
> > checking build system type... i686-pc-linux-gnu
> > checking host system type... i686-pc-linux-gnu
> > checking target system type... i686-pc-linux-gnu
> > checking for gcc... gcc
> > checking for C compiler default output... configure: error: C compiler
> > cannot create executables
> >
> > Has somebody an idea to solve this problem ???
>
>  Review config.log? There are many different possible reasons for this:
>  no write permission in current directory, auxiliary compiler packages
>  (such as binutils) not installed etc.
>
>
>






reply via email to

[Prev in Thread] Current Thread [Next in Thread]