I can’t remember how many times I built SciDB from sources and it is never painless. This time I got a clean machine (Centos 6.5) and tried to follow the steps verbatim. Long story short: If I make locally only using staging directory, it works ok. For cluster deployment, I need to use
which is great, except that run.py install wipes everything from /opt/scidb/14.3, including 3rdparty which has boost in it, because that’s where the prepare toolchain stuff put it.
For the record, “./run.py make” finished successfully (I think).
"./run.py install" complained about missing boost
- prepare toolchain puts boost into /opt/scidb/14.3/3rdparty
- run.py setup # does its stuff
- run.py make # does it and finishes well
run.py install # wants to clear everything from /opt/scidb/14.3
when I don’t agree, it stops
when I do agree, it cleans out /opt/scidb/14.3 INCLUDING 3rd PARTY STUFF*
and then it complains about missing boost
There is a hole in the bucket, dear Liza …
First problem show up when it tries building (why, didn’t make already make it?) Arena.cpp.o
boost/utility.hpp missing, No duh, install wiped out 3rdparty…
So, I probably am missing some simple detail, and once Alex or Paul set me straight I shall probably feel very embarrassed.