Daniel Vrcic wrote: > Isn't that strange that _all_ C compiles (including some bigger > apps like kernel, mplayer, glib, gtk+) went fine apart from only > few C++'s (I think two)?
Maybe because c++ compilation eats loads of memory and thus hits the fishy parts? > If I have a hardware issue, how come > that compilation of those programs always break, and always on > the same file and line of certain source? Maybe a broken compiler. Try recompiling your toolchain (binutils, glibc, gcc) without the funny stuff in the CFLAGS, twice. Then try compiling the failing packages again. > Please, any more tips, advices? Pull out two of the RAM modules and use only one, trying each of them in turn. Make sure you have enough swap (500 MB will do). Maybe all modules are individually okay but can't work together. Benno -- gentoo-user@gentoo.org mailing list
