[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Why does 'configure' look for localhost-g++ ???
From: |
Ralf Corsepius |
Subject: |
Re: Why does 'configure' look for localhost-g++ ??? |
Date: |
18 Apr 2003 07:47:27 +0200 |
Am Fre, 2003-04-18 um 04.25 schrieb Dr. David Kirkby:
> I have written a script (~280 lines):
>
> The config.log is intersting
> http://www.medphys.ucl.ac.uk/~davek/config.log
The config.log contains this log-message:
[..]
$ /export/home/davek/sparrow/atlc-4.3.1/configure --host=sparrow
[..]
The --host=sparrow is the culprit for your problem.
--host is not meant to take the name of an indiviual host, but to take
the canonicalization-triple of you host-system iff cross compiling
[E.g. if cross compiling for an i386-pc-linux-gnu system, you want to
use something similar to this:
./configure --build=`./config.guess` --host=i386-pc-linux-gnu]
> as it seem to find things like /usr/local/bin/gawk,
> /usr/local/bin/install, but then looks for sparrow-g++, sparrow-c++
> etc.
autoconf/configure is correct in searching for sparrow-<tool>, because
you told your the configure script to do so.
> Someone might hopefully see the problem, or if not it might be useful
> in its current state to others.
Just removing the --host from your call to configure above should do
what you want.
Ralf
Re: Why does 'configure' look for localhost-g++ ???,
Ralf Corsepius <=