This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Proposal: Require that GAS be built before GCC in a unified tree
- From: Michael S. Zick <mszick at goquest dot com>
- To: Nathanael Nerode <neroden at twcny dot rr dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Sat, 1 Mar 2003 07:38:23 -0600
- Subject: Re: Proposal: Require that GAS be built before GCC in a unified tree
- References: <20030301050932.GA4263@doctormoo> <20030301051157.GA2221@nevyn.them.org>
- Reply-to: mszick at goquest dot com
On Friday 28 February 2003 11:11 pm, Daniel Jacobowitz wrote:
> On Sat, Mar 01, 2003 at 12:09:32AM -0500, Nathanael Nerode wrote:
> > The point of this proposal is that GCC's configure.in has a ludicrous
> > number of tests for assembler features which split into two: one if
> > there's an actual assembler to test, one if it hasn't been built yet
> > (which does hairy version-number examination).
> >
> > If we required that GAS build before GCC in a unified tree, we could
> > eliminate that half of the code, and just use the standard tests on the
> > newly built gas. It would be a great savings in clarity.
> >
> > What do people think?
>
> Don't you need the version number grubbing anyway for a host-x-host
> build, if you can't run the newly built GAS?
>
Build both the current-machine and the cross-machine binutils first.
Mike