Hello,<div><br></div><div>Through my search of the archives I have come across similar problems such as mine. However, after having tried several suggestions and still remaining unsuccessful, I have decided to post my dilemma. </div>

<div><br></div><div>Basically, I have successfully compiled OpenMPI with the following configuration parameters</div><div><p class="MsoListParagraph" style="text-align:justify;line-height:200%"><span style="font-size:10.0pt;line-height:200%;font-family:Courier">shell$ ../configure
--prefix=/home/vcoralic --enable-static --disable-shared F77=nagfor FC=nagfor
FCFLAGS=-mismatch</span><span style="font-size:10.0pt;line-height:200%;
font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;"></span></p><p class="MsoListParagraph" style="text-align:justify;line-height:200%"><span style="font-size: 10pt; line-height: 200%; "><font class="Apple-style-span" face="arial, helvetica, sans-serif">I have also successfully executed a parallel job by directly invoking <span class="Apple-style-span" style="font-family: Courier; ">mpirun</span>. However, when I try using the queuing system on the cluster, <span class="Apple-style-span" style="font-family: Courier; ">qsub</span>, for a job on say 8 processors, I get the following set of error messages (8 total)</font></span></p>

<p class="MsoListParagraph" style="text-align:justify;line-height:200%"><span style="font-size:10.0pt;line-height:200%;font-family:Courier"><span class="Apple-style-span" style="font-family: arial, sans-serif; line-height: normal; border-collapse: collapse; "></span></span></p>

<div><font class="Apple-style-span" face="&#39;courier new&#39;, monospace">./hello_f90: error while loading shared libraries: libf52.so.1: cannot open shared object file: No such file or directory</font></div><div><font class="Apple-style-span" face="&#39;courier new&#39;, monospace">./hello_f90: error while loading shared libraries: libf52.so.1: cannot open shared object file: No such file or directory</font></div>

<div><font class="Apple-style-span" face="&#39;courier new&#39;, monospace">./hello_f90: error while loading shared libraries: libf52.so.1: cannot open shared object file: No such file or directory</font></div><div><font class="Apple-style-span" face="&#39;courier new&#39;, monospace">./hello_f90: error while loading shared libraries: libf52.so.1: cannot open shared object file: No such file or directory</font></div>

<div><font class="Apple-style-span" face="&#39;courier new&#39;, monospace">./hello_f90: error while loading shared libraries: libf52.so.1: cannot open shared object file: No such file or directory</font></div><div><font class="Apple-style-span" face="&#39;courier new&#39;, monospace">./hello_f90: error while loading shared libraries: libf52.so.1: cannot open shared object file: No such file or directory</font></div>

<div><font class="Apple-style-span" face="&#39;courier new&#39;, monospace">./hello_f90: error while loading shared libraries: libf52.so.1: cannot open shared object file: No such file or directory</font></div><div><font class="Apple-style-span" face="&#39;courier new&#39;, monospace">./hello_f90: error while loading shared libraries: libf52.so.1: cannot open shared object file: No such file or directory</font></div>

<div><br></div><div>where <font class="Apple-style-span" face="&#39;courier new&#39;, monospace">libf52.so.1</font> is shared object file belong ton the NAG Fortran compiler.</div><div><br></div><div>Now, I think I know what the problem is. Basically, the NAG Fortran compiler and its libraries are only available on the master node so that the remaining nodes cannot access/find the required files. From my understanding, the only way to fix this would be put to copy the NAG Fortran compiler to all of the nodes in the cluster. Is that correct?</div>

<div><br></div><div>Or, I suppose that a possible workaround would be to create a symbolic link on all of the nodes through which each node could access the NAG Fortran components available on the master node. This would additionally require that the LD_LIBRARY_PATH be modified on all of the nodes so that the address of the symbolic link be included globally (for all nodes).</div>

<div><br></div><div>The bottom line is that I am looking for some guidance on how to properly fix the above error. I have a feeling that conceptually both of the above ideas may work. However, at this time I am a bit hesitant to begin implementing them since I am not absolutely sure that I know what I am doing or that these &quot;fixes&quot; will work. It also doesn&#39;t help that others use this cluster and I&#39;d hate to be the one that breaks the whole thing down so that no one can use it.</div>

<div><br></div><div>I appreciate any feedback that you can give me!</div><p></p>-- <br>Vedran Coralic<br>
</div>