[SPARCbook] Need sparcbook2 solaris 1.0.1 gcc later than 2.1

[BSD Bob]

> Greetings ...

Greetings...

> > >   Why don't you compile gcc or egcs yourself ? It may take some time but
> > > you could let the machine run overnight or so...
> >
> > Been there, done that, and the original gcc 2.1 port has internal compiler
> > errors and grinds to a screeching halt on 2.5.8, or 2.7.2.3.  It does
> > compile simple things like make and bison and flex.  But, way down in
> > gcc or anything really big, it halts.
> 
> Does it say anything useful ? I had some similar problem on a hp300 with netbsd
> where big projects tended to end with an internal compiler error saying
> "virtual memory exhausted" ( with 16MB RAM and 100MB swap... ) where a simple
> limit off did the trick.

No, it just says ``internal compiler error'' and then exits.

My hack to get around the problem was to reboot the machine each time that
happened, then restart the compile.  That worked but was veddy slow.
A faster hack was just to ``vi INSTALL'' each time it crashed, do a :wq
then restart the compile.   Obviously, it is a memory error problem and
endemic to Sun.  Way down deep in the gcc INSTALL was a short note about
the Sun alloca being broken.... I would say well broken.  But, the sparcbook
is now happily puffing along on gcc-2.5.8, and has now got apache going.

A precompile would have saved me a couple of days, but, no sweat.
It now seems to run fine, after restarting the compile in stage 1
about 30 times.  Stage 2 only bombed twice.

I gotta find out more about that memory problem, and see if it may require
other fixes.

> Hmm, when you use c++ or objective-C then you would certainly want something
> above 2.7

All the C++ I need is sufficient to compile groff and apache.  The rest is
pretty generic C.  With sufficient gnu tools and the like, and it seems mostly
to be purring right along.

Thanks

Bob