Re: A bug in gnat/gcc 3.3.3?

["Adrian Hoe" <byhoe@greenlime.com>]

> I tried to compile the dgate.adb in GtkAda-2.2.1 with gnat/gcc 3.3.3
> under SuSE Linux 9.1 Pro and I got an error:


After reading all these posts, I am tired of the chaos in the Ada
world. I love Ada so much but I hate the compiler (gnat) so much. I
failed to bootstrap a working gnat in Solaris 9. After lots of effort,
I finally got through. But then, I faced the problem of tasking due to
some kind of Solaris 9 thread architecture. Forced to switch back to
Solaris 8. (See my earlier post a few months ago.)

I think one of the problem contributing to the unpopularity of Ada is
the availablity of a fully functional compiler. What good a software is
provided free but contains a bug in it and user has to build themselve
from other source(s). Gnat is one good example.

Why 3.15p? Why 3.3.x? Why 3.4? Why PolyORB? Why this? Why that? Why
can't we just have one single standard? If gnat is going to advance
into 3.3.x, 3.4 and beyond, then make it work. Why still keep 3.15p?
And you can't bootstrap 3.15p from 3.3.3, for example.

I wonder what's happening at gnu/gcc. Why hadn't they tested the
compiler before rolling into public? I can't even find my problem in
"Known Issues" in gnat/gcc documentation.

The chaotic compiler standards will break the spirit of a newbie!

I think the Ada community should take the initiative to standardize
builds if gnu/gcc cannot manage this alone. This initiative will make
Ada more viable in serious development and as well as making learning
Ada more comfortable and hassle-free.

We all have a day time job with limited evening hours. If everyone
would contribute an hour a day, there will be a lot of man-hour per
day. I am willing to contriubte.


Adrian Hoe