I compiled gcc 18.104.22.168 from the sources on prep.ai.mit.edu and haven't
noticed any problems with it. I've used it to compile Linux 2.0.20,
2.0.21, 1.99.4, 2.1.0, 2.1.1, 2.1.3, 2.0.23, 2.1.5, 2.1.6, 2.1.7, and
2.1.8, as well as various applications, without getting those errors. If
you also used that binary from sunsite, perhaps it's just that that's
horked. If not, perhaps it's something about the Linux 2.0.24/25 sources
that brings out the dark side of gcc.
Trevor Johnson <firstname.lastname@example.org>