Should master branch build under docker-compose build ?

[knighan]

Step 10/13 : RUN cd SHEEP/backend/build; make run-sheep-server
---> Running in 0c1bae4f9fe1
Scanning dependencies of target run-sheep-server
[ 0%] Building CXX object applications/CMakeFiles/run-sheep-server.dir/server/run-sheep-server.cpp.o
In file included from /usr/include/c++/7/bits/uniform_int_dist.h:35:0,
from /usr/include/c++/7/bits/stl_algo.h:66,
from /usr/include/c++/7/algorithm:62,
from /SHEEP/backend/applications/server/run-sheep-server.cpp:4:
/usr/include/c++/7/limits:1602:7: internal compiler error: Illegal instruction
max() _GLIBCXX_USE_NOEXCEPT { return FLT_MAX; }
^~~

[nbarlowATI]

Hi @knighan , thanks for reporting this - it ought to work, we will investigate...

[nbarlowATI]

Hi again @knighan - apologies for the delay in responding to this... I wasn't able to reproduce this problem (though did come across a different problem on master related to matplotlib versions).

However, we just pushed quite a few new developments onto master from the development branch. If you try again now, could you let us know if master builds+works for you?
Many thanks!

[stmario]

Hi @nbarlowATI
I just experienced the same problem on MacOs and Ubuntu (VM) with the branches master, wahc_demo and develop.

[pjattke]

Could it be that the problem is somehow related to how GMP is compiled? See this bugreport:

If you don't disable the assembly code in GMP, GMP defaults to basically doing -march=native . You need to configure GMP correctly if you are going to use it across different machines which are different processor types.

[nbarlowATI]

Hi all,
apologies once again for the slow reply - for some reason I'm not getting notifications on this thread.
I still couldn't reproduce this - I just tried on a fresh Ubuntu VM and everything worked fine, and I then removed all related images from my OSX machine, and it worked there as well.

The fact that it is a compiler command does indeed suggest something hardware/architecture related.

The only thing I can think of to debug further would be to try building the sheep_base docker image on the same machine as the docker-compose build command is failing on:

cd backend
docker build -it turingsheep/sheep_base:v3 -f Dockerfile_sheep_base .
cd ..
docker-compose build

This way all compilers/GMP binaries etc. should be consistent.

(But since the systems it's failing on are the same ones that I've tried, I'm not at all sure what is going on...)