Re: GNAT nightmarre

[Michael Matz <matz at suse dot de>]

Hi,

On 28 Jan 2003, Gabriel Dos Reis wrote:

> | > Sure I do mean it.  Witnesses: I was only able to have
> | > maintainer-scripts/gcc_release run normally only -after- removing
> | > *all* instances of GNAT compilers from my $PATH.
> |
> | If you don't have an existing GNAT compiler, the build machinery
> | disables building of GNAT.  Perhaps that's why it worked for you?
>
> That is curious because I got a working GNAT compiler both
>   1) by manual build as expained in the documentation
>   2) automated build as per contrib/gcc_build (I verified)

The point is: without a GNAT compiler anywhere reachable by the build
process the .adb files in gcc/ada/ can't be built.  Because those
constitute a good part of the Ada compiler you can't build that compiler
without having GNAT already somewhere.  If you removed _all_ GNAT's from
your system you simply can't have built a GNAT compiler, there is simply
no possibility to do that.  What could have happened though is, that you
only changed your $PATH to "hide" your GNAT, and that $PATH got reset
somehow (e.g. through shell startup scripts), so that it was found again.

What also could be possible (it can't be ruled out by the information you
gave) is, that you already built an intermediate Ada compiler, until it
broke the build process, then removed your system GNAT, but did fail to
remove the intermediate version, which later could have been used.  Hard
to tell.  Possibly you have the builddir in your path or so.  Whatever, if
you have nowhere a GNAT, and start from a clean build dir, you can't have
ended up with any GNAT version.  Look in your buildlogs, which gnat was
used to compile all the .adb files in gcc/ada/ ?  And you started from a
clean build dir?


Ciao,
Michael.