SuSE gcc blows up

[richb at pioneer.ci.net]

> As I mentioned before, I am running SuSE 6.4, and would like to try it on 
> one of my systems. I have found SuSE releases to be very stable, and 
> their update data base is directly accessable through their system config 
> utility, YAST.

Whoever made the suggestion about checking system memory wasn't far off
the mark.  Last night I installed a new tape drive and rebooted the system.

This morning when I saw the request for a copy of a program which causes
this problem, I tried recompiling (for example, Amanda 2.4.2 from
SourceForge.com, or flex 2.5.4) and couldn't reproduce the error.

So, somehow system memory did get corrupted in such a way that the O/S
and most apps were running but gcc failed.

This isn't SuSE's fault, most likely--I'm running on a 2.2.16 kernel which
I compiled over the weekend.  Maybe there is something hosed with the
kernel config.

Thanks for the offers to help!  I'll write again if I learn more about the
2.2.16 flakeout.

Next step:  figuring out how to get Amanda to deal with large (>2Gb)
filesystems...

cheers,
-rich
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).