Bug #16873
closedg++: internal compiler error: Killed (program cc1plus)
0%
Description
System: OS X 10.10.5
Virtual Machine: Parallel Desktop 11.2
Virtual Machine: CentOS 7
Ceph Version: Hammer branch
Virtual Machine Configurations: 2 CPU, 4G Memory
When I use make -j, this issue occurs:
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugzilla.redhat.com/bugzilla> for instructions.
make3: * [mon/Monitor.lo] Error 1
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugzilla.redhat.com/bugzilla> for instructions.
make3: [mon/PaxosService.lo] Error 1
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugzilla.redhat.com/bugzilla> for instructions.
make3: [mon/PGMonitor.lo] Error 1
make3: Leaving directory `/home/ceph/ceph/src'
make2: [all-recursive] Error 1
make2: Leaving directory `/home/ceph/ceph/src'
make1: [all] Error 2
make1: Leaving directory `/home/ceph/ceph/src'
make: * [all-recursive] Error 1
Updated by Haomai Wang over 7 years ago
I think you don't have enough memory to compile, please check dmesg output
Updated by Nathan Cutler over 7 years ago
So, the compilation succeeds if the machine has 8G of memory? And it succeeds if you omit -j? Both of these would be expected.
Updated by Yutong Liang over 7 years ago
Nathan Cutler wrote:
So, the compilation succeeds if the machine has 8G of memory? And it succeeds if you omit -j? Both of these would be expected.
It works without using -j
Updated by Yutong Liang over 7 years ago
Haomai Wang wrote:
I think you don't have enough memory to compile, please check dmesg output
Thx.
Updated by Nathan Cutler over 7 years ago
-j causes make to compile stuff in parallel, which increases the memory demands.
If you have two CPUs/cores, you can hope to increase speed by passing -j2 to make, but make will happily use up all available memory in this way, so you have to be careful.
Updated by Samuel Just over 7 years ago
- Status changed from New to Rejected
Unless this is happening in the upstream infrastructure, this doesn't seem to be a ceph bug.