This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GNAT nightmarre
- From: dewar at gnat dot com (Robert Dewar)
- To: dewar at gnat dot com, gdr at integrable-solutions dot net
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 28 Jan 2003 00:31:37 -0500 (EST)
- Subject: Re: GNAT nightmarre
> Does that mean that if I have an instance of gnatbind, *freshly built*,
> in my PATH and I'm building a new GNAT compiler (same source as the
> one previously built gnatbind), then inevitably I'll get into trouble?
Yes, that does mean that, you must not put the new gnatbind onto your
path until the new compiler is there to match it. It is critical that
the compiler and binder always be of the same generation. But I am not
100% sure of what your procedure is, so it is still not clear where
the problem lies.
> ell, I hope invoking contrip/gcc_build is considered normal build...
Certainly seems like it should be ...