Re: Why does 'configure' look for localhost-g++ ???

[Dr. David Kirkby]

Earnie Boyd wrote:
> 
> Dr. David Kirkby wrote:
> >
> > But I'm not doing that. I'm trying to run the script on the local
> > host, so I can't be cross-compiling. In fact, it works fine if I run
> > my script via ssh on a 32-bit Linux PC from a 64-bit Sun running
> > Solaris, but running it on the local host fails!!!!
> >
> 
> So don't use --host at all.  
It was suggested to me by Robert Collins, that's why I did it. As far
as I can see from the documentation, the --host option was not needed,
but as Robert's suggestion I did try it. 

> The mere fact that you do indicates that
> you are cross-compiling.  If I'm on host foo (and host meaning what is
> defined by config.guess and config.sub) and specify host bar then I'm
> cross-compiling binaries for use on host environment bar.  

I follow that. 

> If I'm on host foo and specify host foo then I'm cross-compiling binaries for 
> use
> on host environment foo.  Using --host is treated the same regardless of
> which host the binaries are for and the configuration process prepends
> the host name to the tool to build for host.  I.E.: --host=foo uses
> foo-gcc and --host=bar uses bar-gcc.
> 
> Earnie.

So it would seem I need neither option here, as I'm not
cross-compiling in any way. I'm running the configure script on host
sparrow, buy means of ssh from host sparrow.
So why does it now work? 

-- 
Dr. David Kirkby,
Senior Research Fellow,
Department of Medical Physics,
University College London,
11-20 Capper St, London, WC1E 6JA.
Tel: 020 7679 6408 Fax: 020 7679 6269
Internal telephone: ext 46408
e-mail address@hidden