Apparently, though unproven, at 00:40 on Tuesday 12 October 2010, Daniel Pielmeier did opine thusly:
> Alan McKinnon schrieb am 12.10.2010 00:26: > > It's none of those apparently. I checked CFLAGS set by the ebuild in the > > emerge log before posting and they looked fine. gcc was last updated a > > month ago and the machine gets updated almost daily. > > > > glibc seems possible but it's a moot point, especially as after > > investigating memory at Mark's suggestion, genlop runs fine now, world > > updates successfully and 2 ./configure errors about aclocal (that I > > didn't even mention before) have gone away. > > > > I should probably start treating this poor machine more like a notebook > > and less like a high performance machine - running flat out almost 24/7 > > is probably outside of it's design spec :-) > > Glad the reason for your problem was found. Time make use of Dell's NBD > support then :) :-) This is what happens with modern reliable hardware - I should have gone for the memory as the very very first step. It's been so long since I've had to deal with dodgy memory on anything, it just didn't occur to me.... I was ready to start looking for weird flags using weird cpu instructions. -- alan dot mckinnon at gmail dot com
