Re: Fwd: Re: help!!!

[Jim Frost <jim at jimfrost dot com>]

Apologies on not replying to the list. An oversight on my part.

The suggestions you gave me in the reply did not work. I am getting the same 
errors, when trying to ./configure any application. As you have stated it is 
a path issue. Any more suggestions?

Many thanks again,


Jim





> > > Ricardo,
> > >
> > > Thanks for the prompt reply, I have the same problem with all
> > > applications that I am trying to install. It is not application
> > > dependent.
> > >
> > > My environment.....................well I have enclosed the
> > > config.log file from a problem install.
> > >
> > > Many thanks again,
> > >
> > > Jim
> >
> >Jim,
> >
> >My comments are interspersed with your response.
> >
> > > On Monday 03 March 2003 18:51, you wrote:
> > > > We need more detail before we can help.  What are you trying to
> > > > build? What environment variables do you have set?
> > > >
> > > > [keep gcc-help in the loop, there are others on the list that know
> > > > more than I]
> >
> >If there was something proprietary in what you sent, I can understand
> >wanting to stay off-list, but this really should be on the list so
> >others can benefit.
> >
> > > This file contains any messages produced by compilers while running
> > > configure, to aid debugging if configure makes a mistake.
> >
> >[...]
> >
> > > configure:2215: checking for gcc
> > > configure:2241: result: usr/bin/gcc
> > > configure:2485: checking for C compiler version
> > > configure:2488: usr/bin/gcc --version </dev/null >&5
> > > ./configure: line 1: usr/bin/gcc: No such file or directory
> >
> >I can tell you right now, this is a big problem.  The configure script
> >is looking for gcc in a relative path from the current working
> >directory.  You have `usr/bin/gcc' not `/usr/bin/gcc'.  Note the
> >leading slash.  The next few lines confirm this.
> >
> > > configure:2491: $? = 127
> > > configure:2493: usr/bin/gcc -v </dev/null >&5
> > > ./configure: line 1: usr/bin/gcc: No such file or directory
> > > configure:2496: $? = 127
> > > configure:2498: usr/bin/gcc -V </dev/null >&5
> > > ./configure: line 1: usr/bin/gcc: No such file or directory
> > > configure:2501: $? = 127
> > > configure:2525: checking for C compiler default output
> > > configure:2528: usr/bin/gcc     conftest.c  >&5
> > > ./configure: line 1: usr/bin/gcc: No such file or directory
> >
> >[...]
> >
> > > configure:2570: error: C compiler cannot create executables
> > > See `config.log' for more details.
> > >
> > > ## ---------------- ##
> > > ## Cache variables. ##
> > > ## ---------------- ##
> > >
> > > ac_cv_build=i686-pc-linux-gnu
> > > ac_cv_build_alias=i686-pc-linux-gnu
> > > ac_cv_env_CC_set=set
> > > ac_cv_env_CC_value=usr/bin/gcc
> >
> >[...]
> >
> >Bingo, again see the missing slash.
> >
> > > ## ----------------- ##
> > > ## Output variables. ##
> > > ## ----------------- ##
> > >
> > > ACLOCAL='${SHELL} /root/aquaosk-2.0/admin/missing --run aclocal-1.7'
> > > AMDEPBACKSLASH='\'
> > > AMDEP_FALSE='#'
> > > AMDEP_TRUE=''
> > > AMTAR='${SHELL} /root/aquaosk-2.0/admin/missing --run tar'
> > > ARTSCCONFIG=''
> > > AUTOCONF='${SHELL} /root/aquaosk-2.0/admin/missing --run autoconf'
> > > AUTODIRS=''
> > > AUTOHEADER='${SHELL} /root/aquaosk-2.0/admin/missing --run autoheader'
> > > AUTOMAKE='${SHELL} /root/aquaosk-2.0/admin/missing --run automake-1.7'
> > > AWK='gawk'
> > > CC='usr/bin/gcc'
> >
> >Bingo, again see the missing slash.
> >
> >The solution appears to be to define The environment variable `CC'
> >with value `/usr/bin/gcc' before running configure.
> >
> >         Bash:
> >         export CC=/usr/bin/gcc
> >
> >         Csh:
> >         setenv CC /usr/bin/gcc
> >
> >Hope that helps,
> >--
> >Ricardo Anguiano
> >http://www.codesourcery.com

-- 
KMail 1.5 KDE 3.1