weird memory/file corruption errors building glibc and other things

Hi,

I get some very strange file corruption errors when building glibc on the A180. Specifically the dependency files end up with weird garbage overwritten in them, and the glibc build fails like this:

ln /home/build/glibc-2.1.95/hppa-linux/obj/dummy.d /home/build/glibc-2.1.95/hppa-linux/obj/stdlib/lshift.d make[3]: @¸œ@¸œ/build/glibc-2.1.95/hppa-linux/obj/dummy.d: Command not found
make[2]: *** [stdlib/subdir_lib] Error 127
make[2]: Leaving directory `/home/build/glibc-2.1.95/glibc-2.1.95'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/build/glibc-2.1.95/hppa-linux/obj'

This seems to be mostly random, because if I remove the offending files and restart the build, it will usually succeed.

I also get lots of other random errors when building other packages. Usually these end up triggering assertions in bash's malloc wrapper code or causing make to segfault or bus error. They are not repeatable, and usually restarting the build makes them go away, at least on the second or third try.

I don't know what other info I can provide. Like I say, the errors are random and seem to be caused by memory corruption, though there are a few places where they tend to get "caught" more often than not.

I am not using swap at all either, because swapping does not work - I get "invalid swap entry" errors on the console and my processes segfault or bus-error more quickly than usual.

[email protected], http://www.linuxcare.com/
Linuxcare. Support for the revolution.