FS#34080 - [chromium] Unable to compile package in clean chroot

Attached to Project: Arch Linux
Opened by John (graysky) - Thursday, 28 February 2013, 23:40 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 05 March 2013, 09:55 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Cannot compile this package from ABS either inside or outside of a clean chroot (devtools). Complete log attached but here are the parts near the error:

CXX(target) out/Release/obj.target/webcore_bindings/gen/webkit/bindings/V8DerivedSources13.o
CXX(target) out/Release/obj.target/webcore_bindings/gen/webkit/bindings/V8DerivedSources14.o
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
make: *** [out/Release/obj.target/webcore_bindings/gen/webkit/bindings/V8DerivedSources05.o] Error 4
make: *** Waiting for unfinished jobs....
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
make: *** [out/Release/obj.target/webcore_bindings/gen/webkit/bindings/V8DerivedSources06.o] Error 4
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
make: *** [out/Release/obj.target/webcore_bindings/gen/webkit/bindings/V8DerivedSources01.o] Error 4
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
make: *** [out/Release/obj.target/webcore_bindings/gen/webkit/bindings/V8DerivedSources03.o] Error 4
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
make: *** [out/Release/obj.target/webcore_bindings/gen/webkit/bindings/V8DerivedSources02.o] Error 4

Additional info:
* package version(s): 25.0.1364.97-1

Steps to reproduce:
% cp -a /var/abs/extra/chromium /scratch
% cd /scratch/chromium
% sudo extra-x86_64-build -c
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Tuesday, 05 March 2013, 09:55 GMT
Reason for closing:  Not a bug
Comment by Dave Reisner (falconindy) - Saturday, 02 March 2013, 22:43 GMT
I think you're running out of memory. Not sure how this would be a chromium bug.
Comment by John (graysky) - Saturday, 02 March 2013, 22:48 GMT
I'll try again keeping on eye on the mem usage. This box has 8 GB by the way and runs a minimal setup (xfce4).
Comment by Evangelos Foutras (foutrelis) - Monday, 04 March 2013, 22:25 GMT
How many concurrent make jobs have you specified in your makepkg.conf's MAKEFLAGS?

I'm thinking that Dave is correct; you seem to be spawning 10+ build jobs and running out of memory (after all, this is C++ we're compiling).
Comment by Dave Reisner (falconindy) - Monday, 04 March 2013, 22:35 GMT
You can look in your logs for for evidence of the oom killer. The fact that you're seeing "killed" and not a segfault or "Terminated" makes me think the kernel is involved.

Fwiw, I just built a new chromium package with no issues.
Comment by John (graysky) - Monday, 04 March 2013, 22:49 GMT
@foutrelis - It is a quad core so just `-j5' is defined in /etc/makepkg.conf
@falconindy - I am trying it again right now and will inspect dmesg and journalctl -xn for clues and also update this flyspray.

Thank you both the suggestions.
Comment by KaiSforza (KaiSforza) - Tuesday, 05 March 2013, 01:03 GMT
@graysky: Also, be sure you're not using /tmp as a builddir if you're running out of memory.
Comment by John (graysky) - Tuesday, 05 March 2013, 01:09 GMT
Successfully built. You guys were spot on about the mem usage. I ran 'free -m -s 60' and watched it drop from over 6 G free to around 3 G throughout the course of the compilation. Dunno what was sapping up the free mem when opened this ticket... Hung process or something. Sage to close the thread and thanks again.

Loading...