Re: tweaks for autoconf 2.50

[Geoff Keating <geoffk at geoffk dot org>]

> Date: Thu, 24 May 2001 00:21:19 -0700
> From: "Zack Weinberg" <zackw@Stanford.EDU>
> Cc: gcc-patches@gcc.gnu.org
> Content-Disposition: inline
> User-Agent: Mutt/1.3.17i
> 
> On Wed, May 23, 2001 at 11:40:29PM -0700, Geoff Keating wrote:
> > 
> > "Zack Weinberg" <zackw@stanford.edu> writes:
> > 
> > > AC_PROG_CC from 2.13 works just fine when
> > > cross-compiling, we know this because the gcc directory has been using
> > > it all along.
> > 
> > I think you'll find that AC_PROG_CC from 2.13 doesn't work, because it
> > uses AC_PROG_CC_WORKS, which requires that the compiler be able to
> > link, and when you have no libc available because you had no compiler
> > to build it then obviously you can't link anything.
> 
> So how come it works just fine for the gcc directory, then?

Because the gcc directory is compiled for the host, but libiberty is
compiled for the target.  You have to have a working host compiler
before you start, but you don't have to have a working target compiler
(otherwise, what would be the point?).

-- 
- Geoffrey Keating <geoffk@geoffk.org>