Hi Justin,

Not enough memory for the number of CPUs/parallel jobs.

Here’s my vagrant VM on OSx:

vagrant@ ~/vpp (master) $ free
              total        used        free      shared  buff/cache   available
Mem:        4146932     2320260      947376       16732      879296     1765252
Swap:        524284       60656      463628
vagrant@ ~/vpp (master) $ cat /proc/cpuinfo | grep "model name"
model name      : Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
model name      : Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
model name      : Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz


/neale

-----Original Message-----
From: <vpp-dev@lists.fd.io> on behalf of "justin pecqueur via Lists.Fd.Io" 
<jpecqueu=cisco....@lists.fd.io>
Reply-To: "Justin Pecqueur (jpecqueu)" <jpecq...@cisco.com>
Date: Thursday, 9 August 2018 at 03:07
To: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io>
Cc: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io>
Subject: [vpp-dev] Build: MacOS with Vagrant compiler crash in "vom"

    Hi,
    
    I'm trying to bring up VPP on OSX using Vagrant and I keep hitting the 
following crash:
    
    >     default: @@@@ Building vom in /vpp/build-root/build-vpp-native/vom 
@@@@
    >     default: make[3]: Entering directory 
'/vpp/build-root/build-vpp-native/vom'
    >     default: Making all in vom
    >     default: make[4]: Entering directory 
'/vpp/build-root/build-vpp-native/vom/vom'
    >     default:   CXX      types.lo
    >     default:   CXX      arp_proxy_binding_cmds.lo
    >     default:   CXX      arp_proxy_binding.lo
    >     default:   CXX      arp_proxy_config_cmds.lo
    >     default:   CXX      arp_proxy_config.lo
    >     default:   CXX      bond_group_binding_cmds.lo
    >     default:   CXX      bond_group_binding.lo
    >     default:   CXX      bond_interface_cmds.lo
    >     default:   CXX      bond_interface.lo
    >     default:   CXX      bond_member.lo
    >     default:   CXX      bridge_domain_cmds.lo
    >     default:   CXX      bridge_domain.lo
    >     default:   CXX      bridge_domain_arp_entry.lo
    >     default:   CXX      bridge_domain_arp_entry_cmds.lo
    >     default:   CXX      bridge_domain_entry_cmds.lo
    >     default:   CXX      bridge_domain_entry.lo
    >     default:   CXX      client_db.lo
    >     default:   CXX      cmd.lo
    >     default:   CXX      connection.lo
    >     default:   CXX      dhcp_client_cmds.lo
    >     default:   CXX      dhcp_client.lo
    >     default:   CXX      hw_cmds.lo
    >     default:   CXX      hw.lo
    >     default:   CXX      inspect.lo
    >     default:   CXX      interface_cmds.lo
    >     default:   CXX      interface.lo
    >     default:   CXX      interface_factory.lo
    >     default:   CXX      interface_ip6_nd_cmds.lo
    >     default: g++: internal compiler error: Killed (program cc1plus)
    >     default: Please submit a full bug report,
    >     default: with preprocessed source if appropriate.
    >     default: See <file:///usr/share/doc/gcc-5/README.Bugs> for 
instructions.
    >     default: Makefile:877: recipe for target 'interface.lo' failed
    >     default: make[4]: *** [interface.lo] Error 1
    >     default: make[4]: *** Waiting for unfinished jobs....
    >     default: make[4]: Leaving directory 
'/vpp/build-root/build-vpp-native/vom/vom'
    >     default: Makefile:386: recipe for target 'all-recursive' failed
    >     default: make[3]: *** [all-recursive] Error 1
    >     default: make[3]: Leaving directory 
'/vpp/build-root/build-vpp-native/vom'
    >     default: Makefile:691: recipe for target 'vom-build' failed
    >     default: make[2]: *** [vom-build] Error 2
    >     default: make[2]: Leaving directory '/vpp/build-root'
    >     default: /vpp/build-data/platforms.mk:20: recipe for target 
'install-deb' failed
    >     default: make[1]: *** [install-deb] Error 1
    >     default: make[1]: Leaving directory '/vpp/build-root'
    >     default: Makefile:473: recipe for target 'pkg-deb' failed
    >     default: make: *** [pkg-deb] Error 2
    > The SSH command responded with a non-zero exit status. Vagrant
    > assumes that this means the command failed. The output for this command
    > should be in the log above. Please read the output to determine what
    > went wrong.
    Any thoughts?
    
    thanks,
    
    --justin
    
    
    

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10081): https://lists.fd.io/g/vpp-dev/message/10081
Mute This Topic: https://lists.fd.io/mt/24235467/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to