mpi mode problem

Member Site › Forums › Rosetta 3 › Rosetta 3 – Build/Install › mpi mode problem

Viewing 1 reply thread
  • Author
    Posts
    • August 30, 2012 at 12:41 am #1390
      Anonymous

        Hey everyone, I’m trying to compile in mpi mode on a cluster. I used:
        ./scons.py bin mode=release extra=mpi

        After entering the command, it gave me this error:
        Running versioning script … fatal: Not a git repository

        But the compiling went on well and gave me “scons: done building targets.” at the end.

        However, when I checked the executable in the rosetta/resetta_source/bin folder, I didn’t find any executable with mpi in it. The executables all ends with .linuxgccrelease or .default.linuxgccrelease. From previous posts, I thought I should get executables with mpi in it. http://www.rosettacommons.org/node/2265

        Can anyone give me some suggestions?

      • August 30, 2012 at 1:10 am #7719
        Anonymous

          try extras=mpi. (note the s in extras).

        • August 30, 2012 at 2:35 pm #7720
          Anonymous

            Morning, Smith. I corrected the error and tried build following the instructions here: http://www.rosettacommons.org/content/how-compile-rosetta-mpi-option. This time the build went well, except always giving me this message:
            g++: -rpath: linker input file unused because linking not done
            g++: /opt/apps/limic2/0.5.4//lib: linker input file unused because linking not done
            The build was done with “scons: done building targets” and now there are both .linuxgccrelease and .mpi.linuxgccrelease executables in rosetta/rosetta_source/bin. I tried to run in mpi mode, but it ended with errors.
            My guess is scons is not linked to mpiCC from the message? Do you have any suggestions?

          • August 30, 2012 at 2:38 pm #7721
            Anonymous

              “g++: -rpath: linker input file unused because linking not done
              g++: /opt/apps/limic2/0.5.4//lib: linker input file unused because linking not done”

              I have no idea what these mean.

              “I tried to run in mpi mode, but it ended with errors.”

              What errors? Did you use mpirun or your system’s equivalent?

            • August 30, 2012 at 7:11 pm #7723
              Anonymous

                I just found out the error was caused by some invisible characters in the running script for my system. Stupid mistake! Now it runs well. It seems these messages “g++: -rpath: linker input file unused because linking not done
                g++: /opt/apps/limic2/0.5.4//lib: linker input file unused because linking not done” don’t affect the compiling.
                Thank you very much for your help, Smith!

            • Author
              Posts
            Viewing 1 reply thread
            • You must be logged in to reply to this topic.