Bug 499810 – dev-util/cmake-2.8.12.2 - internal compiler error: Killed (program cc1plus) - [Source/CMakeFiles/CMakeLib.dir/{cmCommands,cmComputeTargetDepends,cmDependsFortran,cmake}.cxx.o] Error 4

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Thomas Deutschmann (RETIRED) 2014-01-30 16:48:01 UTC]

Hi,

emerging dev-util/cmake-2.8.12.2 failed:

x86_64-pc-linux-gnu-g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.gentoo.org/> for instructions.
Source/CMakeFiles/CMakeLib.dir/build.make:169: recipe for target 'Source/CMakeFiles/CMakeLib.dir/cmCommands.cxx.o' failed
make[2]: *** [Source/CMakeFiles/CMakeLib.dir/cmCommands.cxx.o] Error 4
make[2]: *** Waiting for unfinished jobs....
x86_64-pc-linux-gnu-g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.gentoo.org/> for instructions.
Source/CMakeFiles/CMakeLib.dir/build.make:330: recipe for target 'Source/CMakeFiles/CMakeLib.dir/cmComputeTargetDepends.cxx.o' failed
make[2]: *** [Source/CMakeFiles/CMakeLib.dir/cmComputeTargetDepends.cxx.o] Error 4
x86_64-pc-linux-gnu-g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.gentoo.org/> for instructions.
Source/CMakeFiles/CMakeLib.dir/build.make:491: recipe for target 'Source/CMakeFiles/CMakeLib.dir/cmDependsFortran.cxx.o' failed
make[2]: *** [Source/CMakeFiles/CMakeLib.dir/cmDependsFortran.cxx.o] Error 4
x86_64-pc-linux-gnu-g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.gentoo.org/> for instructions.
Source/CMakeFiles/CMakeLib.dir/build.make:2308: recipe for target 'Source/CMakeFiles/CMakeLib.dir/cmake.cxx.o' failed
make[2]: *** [Source/CMakeFiles/CMakeLib.dir/cmake.cxx.o] Error 4
make[2]: Leaving directory '/var/tmp/portage/dev-util/cmake-2.8.12.2/work/cmake-2.8.12.2_build'
CMakeFiles/Makefile2:1374: recipe for target 'Source/CMakeFiles/CMakeLib.dir/all' failed
make[1]: *** [Source/CMakeFiles/CMakeLib.dir/all] Error 2
make[1]: Leaving directory '/var/tmp/portage/dev-util/cmake-2.8.12.2/work/cmake-2.8.12.2_build'
Makefile:143: recipe for target 'all' failed
make: *** [all] Error 2

Please see the attached build log for more details.

Reproducible: Always




# emerge --info =dev-util/cmake-2.8.12.2
Portage 2.2.8 (default/linux/amd64/13.0, gcc-4.8.2, glibc-2.18-r1, 3.10.28 x86_64)
=================================================================
                         System Settings
=================================================================
System uname: Linux-3.10.28-x86_64-Intel-R-_Core-TM-_i7-3770K_CPU_@_3.50GHz-with-gentoo-2.2
KiB Mem:     4050884 total,   3830128 free
KiB Swap:    1048572 total,   1041620 free
Timestamp of tree: Thu, 30 Jan 2014 10:45:01 +0000
ld GNU ld (GNU Binutils) 2.24
app-shells/bash:          4.2_p45-r1
dev-lang/python:          2.7.6, 3.3.3
dev-util/pkgconfig:       0.28
sys-apps/baselayout:      2.2
sys-apps/openrc:          0.12.4
sys-apps/sandbox:         2.6-r1
sys-devel/autoconf:       2.69
sys-devel/automake:       1.13.4, 1.14.1
sys-devel/binutils:       2.24-r2
sys-devel/gcc:            4.8.2
sys-devel/gcc-config:     1.8
sys-devel/libtool:        2.4.2
sys-devel/make:           4.0-r1
sys-kernel/linux-headers: 3.11 (virtual/os-headers)
sys-libs/glibc:           2.18-r1
[...]
MAKEOPTS="--jobs --load-average 8"

[Comment 1 Thomas Deutschmann (RETIRED) 2014-01-30 16:48:20 UTC]

Created attachment 369140 [details]
build.log

[Comment 2 Alex Xu (Hello71) 2014-01-30 16:58:22 UTC]

Please attach dmesg.

[Comment 3 Thomas Deutschmann (RETIRED) 2014-01-30 17:21:03 UTC]

OK, this seems to be a strange parallel build issue:

When I use a fixed hard limit like

  MAKEOPTS="-j30"

works fine but when I use a non-fixed hard limit like

  MAKEOPTS="--jobs --load-average 8"

I often (not always) run into this problem.

[Comment 4 Chí-Thanh Christopher Nguyễn 2014-01-30 17:34:28 UTC]

This could be due to an invocation of the OOM killer. That is why dmesg output was asked for.

[Comment 5 Thomas Deutschmann (RETIRED) 2014-01-30 18:03:25 UTC]

Created attachment 369144 [details]
dmesg output

Yup, it was the OOM killer. Thanks.

So I think this is not a general problem and the bug report should be closed as invalid or should it stay?

[Comment 6 Alex Xu (Hello71) 2014-01-30 19:08:15 UTC]

Consider -j8 and removing -pipe.