rsa4046 Posted January 29, 2017 Report Share Posted January 29, 2017 I'm working on a new funtoo install on an older core2 machine, running nicely so far, but I can't seem to rebuild sys-devel/llvm-3.9.1 or sys-devel/llvm-3.9.1-r1. Oddly, I was somehow able to build this version initially, but am now having segfaults in which the emerge fails with (e.g.), /var/tmp/portage/sys-devel/llvm-3.9.1/work/llvm-3.9.1.src/include/llvm/ADT/iterator.h:178:73: internal compiler error: Segmentation fault I've posted more of the tail of the build.log here: https://dolomit.geo.uni-bremen.de/owncloud/index.php/s/7kfsyL9faRQhCaI The message asks that I Please submit a full bug report, with preprocessed source if appropriate. See <http://bugs.funtoo.org> for instructions." but I wanted to inquire if anyone had any suggestions before proceeding. I've tried rebuilding several times (also tried setting MAKEOPTS="-j1"), always failing, although not necessarily at the same place. My funtoo profile is # epro show === Enabled Profiles: === arch: x86-64bit build: current subarch: core2_64 flavor: server mix-ins: kde-plasma-5 mix-ins: console-extras mix-ins: dvd mix-ins: print === All inherited flavors from server flavor: === core (from server flavor) minimal (from core flavor) and /etc/make.conf is fairly empty: MAKEOPTS="-j3" VIDEO_CARDS="nouveau" INPUT_DEVICES="evdev" USE="X pdf jpeg" CHOST="x86_64-pc-linux-gnu" The complete build log is of course too large to post, but again is available in the folder linked here https://dolomit.geo.uni-bremen.de/owncloud/index.php/s/7kfsyL9faRQhCaI emerge.info is here emerge.info.txt build.log tail is here llvm.txt Thanks for any ideas any one can offer. Link to comment Share on other sites More sharing options...
hencb Posted January 29, 2017 Report Share Posted January 29, 2017 Hi! I'd suggest posting a bug on bugs.funtoo.org, it's the right place to handle build failures. Segmentation faults are caused by insufficient memory. https://bugs.funtoo.org/browse/FL-3503 Rule of thumb: ~1.25GB per thread. Try compiling with MAKEOPTS="-j1" Also, you might want to read up on how to debug such build failures: https://wiki.gentoo.org/wiki/Sakaki%27s_EFI_Install_Guide/Building_the_Gentoo_Base_System_Minus_Kernel#Troubleshooting_a_Failed_Build If your hard drive, CPU or memory are faulty, this is going to show when compiling llvm. https://bugs.funtoo.org/browse/FL-3498 I suggest running with -j1 and making sure the swap is turned on, and leave it to compile overnight. I'd run memtest, check SMART for the hard drive, and there's mprime for the CPU or equivalent. I'll try emerging llvm on a core2 system I have and report the results. Link to comment Share on other sites More sharing options...
rsa4046 Posted January 30, 2017 Author Report Share Posted January 30, 2017 Hi! I'd suggest posting a bug on bugs.funtoo.org, it's the right place to handle build failures. Segmentation faults are caused by insufficient memory. https://bugs.funtoo.org/browse/FL-3503 Rule of thumb: ~1.25GB per thread. Try compiling with MAKEOPTS="-j1" Also, you might want to read up on how to debug such build failures: https://wiki.gentoo.org/wiki/Sakaki%27s_EFI_Install_Guide/Building_the_Gentoo_Base_System_Minus_Kernel#Troubleshooting_a_Failed_Build If your hard drive, CPU or memory are faulty, this is going to show when compiling llvm. https://bugs.funtoo.org/browse/FL-3498 I suggest running with -j1 and making sure the swap is turned on, and leave it to compile overnight. I'd run memtest, check SMART for the hard drive, and there's mprime for the CPU or equivalent. I'll try emerging llvm on a core2 system I have and report the results. Hi, sorry for the late reply. Thanks so much for the kind advice -- I am giving these a shot ... will post back ASAP. Cheers!! Link to comment Share on other sites More sharing options...
hencb Posted February 7, 2017 Report Share Posted February 7, 2017 Hi, sorry for the late reply. Thanks so much for the kind advice -- I am giving these a shot ... will post back ASAP. Cheers!! Hey no problem, that's what the forums are for, just leave a message and come back anytime. Did the suggestion fix your problem compiling? Link to comment Share on other sites More sharing options...
rsa4046 Posted February 15, 2017 Author Report Share Posted February 15, 2017 Turned out: shifting back to gcc:4.9 from gcc:5 did the trick ... still don't quite understand the error, but the RAM passed memtest, so ... only thing left to try was the compiler. Thanks again for all your help! Link to comment Share on other sites More sharing options...
hencb Posted February 25, 2017 Report Share Posted February 25, 2017 Did you follow http://www.funtoo.org/News:GCC_Update? Revdep-rebuild is a required step for the upgrade to gcc 5 Link to comment Share on other sites More sharing options...
Recommended Posts