Created attachment 303119 [details] output of emerge --info I tried to merge app-emulation/virtualbox-4.1.8-r1 with the following USE settings: [ebuild N ] app-emulation/virtualbox-4.1.8-r1 USE="additions alsa opengl pam python qt4 sdk -doc -extensions -headless -java -pulseaudio -vboxwebsrv -vnc" The compiling procedure stops at some point when compiling translate.o. The error message shows that it is the emake that fails. Here also attached the output of emerge --info command. I'm not sure is it a configuration issue on my side or a bug? Any input appreciated.
Created attachment 303123 [details] build log file of the merge process
Did you enable the "nopie" USE flag (or any other USE flag marked clearly as "NOT FOR GENERAL USE") when compiling gcc? I guess "nopie" USE flag on gcc is the reason you get all these "i686-pc-linux-gnu-g++: unrecognized option '-nopie'". I'm however uncertain whether the "Internal error: Killed (program cc1)" is related to it. Does the older =virtualbox-4.1.8, which does not contain virtualbox_nopie.patch, work for you?
Oh, yeah, probably you ran out of memory when compiling virtualbox, which would result in cc1 being killed. You could find the actual reason from your kernel log or dmesg.
(In reply to comment #3) > Oh, yeah, probably you ran out of memory when compiling virtualbox, which would > result in cc1 being killed. You could find the actual reason from your kernel > log or dmesg. Oh yes, dmesg shows that there was not enough memory for stack. I'm just curious about how much memory it needs. It's not a high end machine, but still 1G ram should be sufficient? I did not use nopie USE flag in my system, I'll have a try definitely.
No, I meant enabling "nopie" on gcc may cause the problem of "i686-pc-linux-gnu-g++: unrecognized option '-nopie'". Sorry for not explaining it clearly. If you did not enable "nopie" when compiling gcc at all, I have no idea why you would get "i686-pc-linux-gnu-g++: unrecognized option '-nopie'". Maybe you should consider asking this question on the forums. As for the run-out-of-memory issue, 1GB memory may not actually be sufficient for MAKEOPTS="-j2". I could compile virtualbox successfully on my computer with 1GB memory + 1GB swap.
You ran out of RAM. Possible solutions: 1) Install more RAM. 2) Set MAKEOPTS=-j1 and no higher. 3) Remove -pipe from CFLAGS.
Thanks for all your help and recommendation. Yes, it was the memory issue. I fixed it by creating a 2G temporary swap file. VirtualBox has been merged.
