Hi Riccardo and all,<br><br>I am extremely sorry if I offended someone. My purpose was definitely not that. <br><br><div class="gmail_quote">On Wed, May 26, 2010 at 11:48 PM, Riccardo Di Meo <span dir="ltr"><<a href="mailto:dimeo@democritos.it">dimeo@democritos.it</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">soumyajyoti haldar wrote:<br>
> Hi,<br>
><br>
> On Wed, May 26, 2010 at 9:11 PM, Riccardo Di Meo <<a href="mailto:dimeo@democritos.it">dimeo@democritos.it</a><br>
</div><div><div></div><div class="h5">> <mailto:<a href="mailto:dimeo@democritos.it">dimeo@democritos.it</a>>> wrote:<br>
><br>
> Vikas Varshney wrote:<br>
> > Dear all,<br>
> > I have a very simple question.<br>
> ><br>
> > I have 2 mpif90 installed on my machine<br>
> > one in /usr/local/bin which does not have fortran support. It says<br>
> > "Unfortunately, this installation of Open MPU was not compiled with<br>
> > Fortran 90 support ..."<br>
> > other one is in my local directory which was installed by me. It<br>
> does<br>
> > have fortran compiler (ifort).<br>
> ><br>
> > When, I try to run configure script to genarate makefile, it assumes<br>
> > mpif90 to be the first one and results in unsuccessful<br>
> configure. So,<br>
> > my question is that how can I direct the configure script to<br>
> look for<br>
> > other mpif90 and the assciated libraries and header files. Where<br>
> do I<br>
> > need to make necessary changes? Or do I need to ask my admin to<br>
> update<br>
> > mpif90 in /usr/local/bin (where I dont have writable access)?<br>
><br>
> Two solutions:<br>
><br>
> There's a MPIF90 environment variable, which can be set to the mpif90<br>
> compiler of your choice. Just point it to your mpif90 binary in your<br>
> home before configuring QE. This is the standard/correct solution.<br>
><br>
> A "one size fits all" solution, which you can use also for other<br>
> similar<br>
> cases ,would be to make your PATH environment variable give precedence<br>
> to the location of the mpif90 compiler you want to use:<br>
><br>
> export PATH=<location of your mpif90>:$PATH [bash]<br>
><br>
><br>
> you need to set correct LD_LIBRARY_PATH also. Otherwise during<br>
> compilation and run time it may pickup the wrong<br>
</div></div>LD_LIBRARY_PATH it's a variable used only at runtime and has nothing to<br>
do withbcompilation (man ld.so for details).<br></blockquote><div><br>Yes I know that LD_LIBRARY_PATH variable used only at runtime. ' compilation ' was just by mistake I wrote. <br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Btw if the MPI implementation is openmpi, LD_LIBRARY_PATH doesn't need<br>
to be changed , as mpirun/mpiexec will set the correct environment<br>
automatically (not to mention implementations like mpich v1, which link<br>
statically by default)...<br></blockquote><div><br>Well , that was the impression I had earlier, that it can set the correct environment. But if the system contains both gcc compiled openmpi ( most common location is /usr/lib/openmpi , iff installed by the OS !!! ) and intel compiled MPI ( installed by user ) then my personal experience tells me to better set the LD_LIBRARY_PATH. openmpi faq's are also telling same thing, ( I found it during the trouble shooting of my problem ). However openmpi can be run without setting the LD_LIBRARY_PATH, provided you always mention the full path . My understanding from the following faqs tails me these. Pls correct me if I am wrong. <br>
<br><a href="http://www.open-mpi.org/faq/?category=running#adding-ompi-to-path">http://www.open-mpi.org/faq/?category=running#adding-ompi-to-path</a> <br><br>But again it's my personal experience . <br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
><br>
> and one personal experience ,by default /usr/bin and /usr/local/bin<br>
> are set as path when u boot up the system.<br>
> and now if you your current mpif90 directory to PATH, it may not pick<br>
> up the correct one. bcoz u have 2 mpif90, one is in /usr/bin , other<br>
> is in some directory in you home. the search order for the mpif90<br>
> depends on which folder path is loaded to your path variable first .<br>
> So if your PATH variable contains the entry of /usr/bin first then<br>
> it'll not pick up the mpif90 from ur home.<br>
><br>
> I made some changes in my .bash_profile as follows<br>
><br>
> line 1 : unset PATH<br>
> line 2 : export PATH="${PATH}:<location of your mpif90>"<br>
> line 3: export PATH="${PATH}:/bin:/usr/bin:/usr/local/bin" and finally<br>
> load "/etc/profile" again<br>
> line 4: source /etc/profile<br>
<br>
</div>Maybe I'm missing something, but besides from using 4 instructions<br>
instead of one, and from adding a stylish ":" in front of your PATH,<br>
what's the added benefit of your suggestion over the compact form<br>
<div class="im"><br>
export PATH=<location of your mpif90>:$PATH<br>
<br>
</div>in my reply?<br></blockquote><div><br>Nothing wrong in your reply. <br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Besides, your suggestion assumes that the definition of PATH comes only<br>
from /etc/profile, which would prevent people accepting it from using<br>
software installed by the administrator in non standard ways (e.g. by<br>
modifying /etc/skel/.bashrc)<br>
<br>
Cheers,<br>
<font color="#888888">RDM<br>
</font><div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
Pw_forum mailing list<br>
<a href="mailto:Pw_forum@pwscf.org">Pw_forum@pwscf.org</a><br>
<a href="http://www.democritos.it/mailman/listinfo/pw_forum" target="_blank">http://www.democritos.it/mailman/listinfo/pw_forum</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Soumyajyoti Haldar, M.Sc<br><br>Junior Research Fellow<br>Advance Computing Laboratory<br>Department of Physics, University of Pune<br>Ganeshkhind, Pune - 411007; INDIA<br>
<br>Tel : (+91 20) 25692678; Extn# 408<br><br>~~~***~~~***~~~***~~~***~~~***~~~***~~~***~~~<br>