Created attachment 394798 [details] emerge --info '=www-client/chromium ...' I've tried "perl-cleaner --reallyall" and it didn't help.
Created attachment 394804 [details] build.log.tar.bz2
Created attachment 394806 [details] emerge -pqv 'www-client/chromium ...
Created attachment 394808 [details] environment
From the log file: ../../third_party/WebKit/Source/core/css/MediaQueryExp.h:95:111: internal compiler error: Segmentation fault Can you check dmesg for any errors please?
I'll add another build.log and the content of 'dmesg'
Created attachment 394822 [details] build.log.tar.bz2
Created attachment 394824 [details] dmesg > _dmesg
The last line of dmesg said: [ 394.120195] tar (3446) used greatest stack depth: 12736 bytes left Does that mean it's out of memory or smth?
Comment on attachment 394804 [details] build.log.tar.bz2 Why did you store a single file in a tar archive?
Comment on attachment 394822 [details] build.log.tar.bz2 Again, compression doesn't need tar.
Comment on attachment 394822 [details] build.log.tar.bz2 And in this case, you seem to have compressed build.log with bzip2, then put it in a tar archive, and then compressed it again.
Comment on attachment 394822 [details] build.log.tar.bz2 And build.log.out says: 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00002800
2 gigabytes RAM with 2 make jobs. You ran out of memory.
I compressed only build.log because it's the only file over 1000K, it's size is 19MB when it's unpacked. I used 'tar cvjpf build.log.tar.bz2 build.log'. I thought that's how it's supposed to be done. I think I typed 'tar cvjpf build.log build.log.tar.bz2' the first time and got it right only in the second time. Maybe that left irregularities in the archive. Sorry :-) About the memory shortage: is there any way for me to fix it? I've got 2GB of RAM and 2GB of swapspace. Or the only solution would be to buy a newer computer?
