An error occurred during the installation

[Anonymous]

Dear Rosetta Users,

I recentlly downloaded the src version of rosetta 2020.50 and compiled it with scons.py, but there was an error. It seems that the program was pointing towards a wrong directory (the bin version directory) for the generate_database_cache application. I’m attaching the log file. Thank you in advance!

[Anonymous]

How are you attempting to set things up with the directory layout? It looks like your Rosetta is installed under `/home/progs/rosetta_src_2020.50.61505_bundle/` Is `/home/progs/rosetta_bin_linux_2020.50.61505_bundle/` anything?

(Note that we don’t really set up Rosetta to be a traditional compile/install split. The default assumption is that you extract Rosetta, compile it in that directory, then run it out of that same directory. There isn’t a separate “install” phase, and there really isn’t a separate install directory. Moving Rosetta after compilation can be tricky and is not recommended unless you really need to – just run it out of the same directory you extracted and compiled it in.)

 

[Anonymous]

Thank you for the comments!

I previously downloaded the bin version of Rosetta and tried to compile the mpi version of the loop modeling applicaitons, but then I decided to use the src version and compile everything from the source code. I deleted the entire directory of the bin version (/home/progs/rosetta_bin_linux_2020.50.61505_bundle). 

When I was compiling from the src version, I just ran the command (./scons.py -j 10 mode=release bin) under the src directory (/home/progs/rosetta_src_2020.50.61505_bundle/main/source) and the error came out from this compilation. It seems this is the only error and everything else was compiled successfully. What can I do to fix it? Thank you!

[Anonymous]

My guess is that you may have the ROSETTA3_DB variable (or similar) set. Run `env | grep ROSETTA`. If a DB variable shows up pointing to the bin directory, that’s your issue.

If you don’t move Rosetta from the compile directory, it’s quite able to find the apprpriate database based on the relative location from executable. As such, there’s no need to set an environment variable or pass the database path on the command line. As such, simply remove the environment variable settings from where ever you have them set. (Typically you .bashrc file, but it depends a bit on how you have your shell set up.)

[Anonymous]

Thank you for the suggestion! I removed the variables and recompiled. There was no error this time. 

[Author]

Posts