## You are here

6 posts / 0 new
#1

Hello,

I am trying to install CSRosetta and Rosetta on a computer running Fedora 20, but I keep on getting the following error message:

/home/crowlab/Rosetta/main/source/bin/AbinitioRelax.linuxgccrelease: error while loading shared libraries: libcifparse.so: cannot open shared object file: No such file or directory

We have CBFlib-0.9.5.1-1.fc20 package installed, but the software seems to not recognize it. We are not sure what we should have installed instead.

Regards,

Marlyn

Category:
Post Situation:
Wed, 2016-06-15 12:08
mwid

cifparse should be included.  It's not linking properly.  What verison are you using?  Do you see "cifparse" in any of the settings files in source/src?

Wed, 2016-06-15 12:13
smlewis

Hi,

Thank you for the speedy reply.

We dowloaded the source and binaries for Rosetta3.6.

When I searched for cifparse in the directory source/src, I found three files: mmCIFParser.cc, mmCIFParser.hh, and mmCIFParser.fwd.hh. I'm not sure what to do with them though.

Regards,

Marlyn

Wed, 2016-06-15 12:49
mwid
~/ROSETTA/Rosetta/main/source/src> grep cifparse *settings
core.2.src.settings:	"cifparse"
core.3.src.settings:	"cifparse"

What does that command return for you?  Try adding cifparse at the bottom of apps.src.settings as it is in core.n.source.settings and recompiling?

3.6 is just one of the weeklies from early April; you can also try a recent weekly and see what happens (not that we've changed this functionality).  Failing that, we can just rip cifparse out, you presumably aren't using it (I hope you aren't since it's not fully functional).

Wed, 2016-06-15 14:28
smlewis

Hi,

I tried the command and it returend the same two lines as your example. I added cifparse in the subprojects of apps.src.settings and recompiled Rosetta. This seemed to work and I am able to run Rosetta now.

Thank you very much. Your help is greatly appreciated.

Regards,

Marlyn

Wed, 2016-06-15 15:31
mwid

Some further rumination from the mailing list:

"The fact that they got a "cannot open file" error when running indicates that they didn't have any problem finding it when linking, but only when running. Best guess is that the directory location changed between compiling and running. (e.g. because they're running from a mounted drive) This means the rpath linkage information in the files may no longer be accurate, and it has a hard time finding the library from the external/ directory.

So I don't actually think that having it in apps fixed the problem, I think it's more the fact that they recompiled which did it."

Thu, 2016-06-16 15:28
smlewis