Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to build Clipper Docker images on Mac with new CI/Infrastructure #621

Closed
withsmilo opened this issue Jan 30, 2019 · 1 comment
Closed

Comments

@withsmilo
Copy link
Collaborator

@simon-mo merged new CI/Infrastructure recently by #595. It looks great to me, but I found a bug.

Dev environment

  • MacBook Pro + Mojave 10.14.3

How to build

$ ./bin/shipyard.sh
$ make -f CI_build.Makefile lib_base

Error messages

 [lib_base] libtool: compile:  g++ -DHAVE_CONFIG_H -I./.. -pthread -I/usr/include -std=gnu++1y -g -O2 -MT Checksum.lo -MD -MP -MF .deps/Checksum.Tpo -c Checksum.cpp -o Checksum.o >/dev/null 2>&1
 [lib_base] g++: internal compiler error: Killed (program cc1plus)
 [lib_base] Please submit a full bug report,
 [lib_base] with preprocessed source if appropriate.
 [lib_base] See <file:///usr/share/doc/gcc-6/README.Bugs> for instructions.
 [lib_base] The command '/bin/sh -c git clone https://github.com/facebook/folly     && cd folly/folly     && git checkout tags/v2017.08.14.00     && autoreconf -ivf     && ./configure     && make -j     && make install' returned a non-zero code: 137
make: *** [lib_base] Error 137
withsmilo pushed a commit to withsmilo/clipper that referenced this issue Jan 30, 2019
* related issue : ucbrise#621
* When we execute 'make -j' command with no argument on Mac, the build process can occur internal compile error. So we need to revert ClipperLibBaseDockerfile.
* Refer to https://unix.stackexchange.com/questions/316644/is-make-j-with-no-argument-dangerous.
withsmilo pushed a commit to withsmilo/clipper that referenced this issue Mar 21, 2019
* related issue : ucbrise#621
* When we execute 'make -j' command with no argument on Mac, the build process can occur internal compile error. So we need to revert ClipperLibBaseDockerfile.
* Refer to https://unix.stackexchange.com/questions/316644/is-make-j-with-no-argument-dangerous.
simon-mo pushed a commit that referenced this issue Mar 28, 2019
* related issue : #621
* When we execute 'make -j' command with no argument on Mac, the build process can occur internal compile error. So we need to revert ClipperLibBaseDockerfile.
* Refer to https://unix.stackexchange.com/questions/316644/is-make-j-with-no-argument-dangerous.
@withsmilo
Copy link
Collaborator Author

withsmilo commented Mar 29, 2019

solved by #622.

rkooo567 pushed a commit to rkooo567/clipper that referenced this issue Apr 27, 2019
* related issue : ucbrise#621
* When we execute 'make -j' command with no argument on Mac, the build process can occur internal compile error. So we need to revert ClipperLibBaseDockerfile.
* Refer to https://unix.stackexchange.com/questions/316644/is-make-j-with-no-argument-dangerous.
rkooo567 pushed a commit to rkooo567/clipper that referenced this issue Apr 28, 2019
* related issue : ucbrise#621
* When we execute 'make -j' command with no argument on Mac, the build process can occur internal compile error. So we need to revert ClipperLibBaseDockerfile.
* Refer to https://unix.stackexchange.com/questions/316644/is-make-j-with-no-argument-dangerous.
rkooo567 pushed a commit to rkooo567/clipper that referenced this issue Apr 28, 2019
* related issue : ucbrise#621
* When we execute 'make -j' command with no argument on Mac, the build process can occur internal compile error. So we need to revert ClipperLibBaseDockerfile.
* Refer to https://unix.stackexchange.com/questions/316644/is-make-j-with-no-argument-dangerous.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant