Re: EGCS-970929 and GNAT-3.10p?

[Jeffrey A Law <law at cygnus dot com>]

  In message <Pine.BSF.3.96.971009075906.24865J-100000@vespucci.advicom.net>you write:
  > If that one person is me, then I have been trying to build gnat-3.10p with
  > the gcc2 test snapshots lately.
Yup.  I was referring to you :-)

  > My early attempts at building with egcs
  > were not successful and I did not look into them vey far since I
  > needed to test egcs on non-Ada platforms at the time.
Well, if you remember what went wrong I might be able to provide some
assistance now (I don't think I saved that message, I guess I could go
wander the archives...).

I started poking at gnat-3.10p with egcs a short while ago -- I got
gnat1 and gnattools built on the PA.  It then died building the
library due to a buglet in the gcc-2.7.2 PA binaries provided by
the GNAT folks.

After working around that and rebuilding, I got gnat1, gnattools
and gnatlib built OK, except for s-taprde, which got a warning
of some kind, then the build stopped.  I disabled that one object
(I've got better things to do right now :-) and the gnatlib build
finished.

I'm going to to a gnat 3-stage overnight, just to see what happens.

BTW -- is it just me, or is the Ada compiler extremely slow?


This was mostly a proof of concept and to give me some home grown gnat
binaries for bootstrapping purposes later.  I'm not going to try to
integrate GNAT into egcs right now (though we do want it long term).

When we do start thinking about integrating GNAT, the big issues will be:

  * GNAT is written in Ada, and thus requires GNAT binaries to bulid itself.

  * The build process isn't exactly "make; make install" :-)  We'll have
  to pull out the runtime and figure out how to deal with gnattools.  I
  suspect there'll be problems with GNAT in cross build environments too.

jeff