Installing Pyrosetta in CentOS6.0

Member Site Forums PyRosetta PyRosetta – Build/Install Installing Pyrosetta in CentOS6.0

  • This topic has 4 replies, 3 voices, and was last updated 11 years ago by Anonymous.
Viewing 2 reply threads
  • Author
    Posts
    • #1749
      Anonymous

        Hi,

        I am trying to install the Pyrosetta, version- Scientific/Red Hat Linux (64-bit) on CentOS 6.0 but I am getting the following error when I use the command from rosetta import * :-

        ImportError: libpython2.7.so.1.0: cannot open shared object file: No such file or directory

        I have also installed python 2.7 , and it’s installed at /usr/local/python2.7. I searched for the libpython2.7.so.1.0 file , but I was not able to locate it. In addition to python 2.7, I also have python 2.6 in the system.

        Pls help


        BHARAT

      • #9485
        Anonymous

          When you searched for the libpython2.7.so.1.0 file, where/how did you search for it?

          My suggestion is to run the command “find /usr -name libpython2.7.so.1.0” and see if that outputs anything. (This may take a while to run.)

          If it does, look at your LD_LIBRARY_PATH environment variable, and check that the directory it’s found in is listed there. If not, you’ll probably need to add it.

        • #9492
          Anonymous

            Can you have your cluster admin install it? https://www.rosettacommons.org/content/problem-glibc-when-installing-pyrosetta-redhat-enterprise-cluster

            What version of PyRosetta are you trying to run?

          • #9491
            Anonymous

              I installed python 2.7 again and made a symlink for the library file, but still I am getting another error :-
              ImportError: /lib64/libc.so.6: version `GLIBC_2.14′ not found (required by rosetta/libmini.so)

            • #9493
              Anonymous

                That sounds like there is something off with your compiler setup — e.g. you have multiple compiler versions installed in such a fashion that they aren’t playing well with each other. Have you installed your own version of gcc? If so, you might have done it in such a way that it conflicts with the system version of gcc.

            Viewing 2 reply threads
            • You must be logged in to reply to this topic.