Re: gcc/gnat 3.3

["Jeff C," <nolongersafeto@userealemailsniff.com>]

"Adrian Hoe" <AdrianHoe@nowhere.com> wrote in message
news:3f9ded55$1_2@news.tm.net.my...
> Adrian Hoe wrote:
>
> > Andreas Almroth wrote:
> >
> >> The developers have changed the way of fiddling with threads (task
> >> control in the run-time) to cater for the change in the thread API in
> >> Solaris 9 in the later 5.01 source tree, but that change does not
> >> really work when incorporated into the GCC tree the way I have tested
it.
> >> The former method was very very specific to how GCC produces the
> >> binaries, and the new method is somewhat less "hack'n'slashy", but I
> >> don't seem to get it to work though.
> >> The fault most likely on my side of course...
> >> Using a "clean" 5.xx would probably be a way to verify...
> >>
> >> BTW, just being curious, would you mind adding some meat on the
> >> "generated too many errors"? Just interested to know what went wrong...
> >
> >
> > I was trying to re-generate the build errors. But I could not get to
> > make bootstrap with Ada although I did:
> >
> > % ../configure --enable-languages=c,ada
> >
> > gnat was not built and I look into Make-lang, Ada was not in there. I
> > don't know why.
> >
> > I am using gcc-3.3.2 instead of 3.3 the last time I tried to build.
>
>
>
> I can't configure to build the gnat in gcc 3.3.2.
>
> With the command below:
>
> % ../configure --enable-languages=c,ada
>
> and I get:
> ...
> checking for compiler driver that understands Ada... (cached) no
> ...
>
> After the configure, I checked Make-lang and Ada is not in there.
>
> Can someone tell me what's going wrong here?
>
> I have gcc 2.95.3 and gnat 3.15p installed on Sun Blade 150/Solaris 9.

There are probably a few was to work around this but the easiest thing is to
ignore you 2.95.3 install (move
out of your path) and bootstrap with 3.15.

Note that it is saying (cached) which means it will not run this test again
so blow away your build
area and start over (easiest way).

Also your configure looks a little strange

../configure

Where are you building from? You should not build from "inside" the source
directories.
I suppose of you made a new directory inside the top most level of the gcc
directory and built
from in there this configure path would make sense.

Finally, make sure you follow all of the other GNAT specific build
instructions from the manual.