I am having an interesting time trying to compile/install the source. I obtained an academic license, and downloaded the latest stable release, but it refuses to compile.
Specs/Details/Code:
Ubuntu 18.04.1
Rosetta 2019.35/31 ( I have tried both )
From terminal I run:
~$: cd my/rosetta/dir/main/source
~$: ./scons.py -j 64 mode=release bin
It attempts to compile - it takes it about 5-10 minutes before it hits an error. I remove necessary files for a reinstall according to this forum as such:
~: cd my/rosetta/dir/main/source
~: rm .sconsign.dblite
~: rm bin/*
~: rm -rf build/*
~: ./scons.py -j 64 bin mode=release
It tries to compile again, and I recieve a new error. Each time I try to build the error is different - which is the frustrating part. The error almost always takes on the form:
Scons: *** [build/src/release/linux/5.0/64/x86/gcc/7/default/protocols/denovo_design/components/*SOME-FILE*] Error1
Where *SOME-FILE* is always differnet - it is never the same on subsequent compiles. It has been ProfileScoreMatrix.os, FileContentsMap.os, IdealAbegoGenerator.os, etc.
It makes me feel like I am not totally undo-ing changes when doing multiple installs/builds. Why else would the compile errors always be different if nothing else is changed? Is there a way to completely wipe the system of any rosetta-related files and do a fresh download/install?
Any help is appreciated,
Nathan
> Why else would the compile errors always be different if nothing else is changed?
You are compiling at j 64 (nice flex BTW), so you have a 64-way race condition. You see whichever problem file the computer happens to hit first, and within your sampling, it happens to keep hitting different ones. I suspect you have a misconfiguration or unsupported compiler (or too-new compiler), so that lots of files hit small issues.
I would try recompiling after deleting NOTHING (just re-issue the compile command, maybe at -j1) to see if it re-hits the same error. We'll need that error message to analyze and debug.
If the downloaded binaries work, why not just use them? Compiling yourself is valuable if you make code changes or need something like mpi. (at j64 maybe you need mpi.)
> Is there a way to completely wipe the system of any rosetta-related files and do a fresh download/install?
You're doing this. You can remove the code itself, of course, and re download it if you wish. Rosetta does not make modifications to your system itself - it just "installs" binaries into its own directories, deleting them is all you do to "uninstall" them.
I'd also ask: do you actually have 64 CPU cores? On most desktops or laptops, -j64 sounds like it's asking for trouble...
(This could also be a disk error. Do you have ~2 G free for the files created during compilation?)
oh, i love this hypothesis