This is the mail archive of the
mailing list for the GCC project.
Re: Updating top-level autoconf to 2.59
- From: Steve Ellcey <sje at cup dot hp dot com>
- To: drow at false dot org
- Cc: gcc-patches at gcc dot gnu dot org, binutils at sourceware dot org
- Date: Thu, 14 Dec 2006 13:14:59 -0800 (PST)
- Subject: Re: Updating top-level autoconf to 2.59
> > > Aha! This is the issue I fixed for subdirectories on 2003-09-21.
> > > I think we shouldn't "fix" this, but I'm open to comments; this
> > > is one of the changes in autoconf we've been putting off.
> > So what would be the 'proper' way to specify a native GCC build on a
> > target without having to use config.guess? For example, on a PA2.0
> > machine config.guess would return hppa2.0w-hp-hpux11.11 but maybe I want
> > to make a PA1.1 compiler (hppa1.1-hp-hpux11.11) on this PA2.0 box so
> > that it will work on PA1.1 boxes as well as PA2.0 boxes. But I want the
> > compiler as gcc, not hppa1.1-hp-hpux11.11-gcc. How should I specify
> > this?
> Just --build or --build= --host=. I'm pretty sure that works for
> autoconf 2.13 too.
> But if you think we ought to keep it the way it is, I can probably come
> up with a workaround.
> Daniel Jacobowitz
I don't feel that strongly one way or the other. I changed my configure
to just specify --build and that seems to be working fine.