<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Alain,<div><br></div><div>Again, thanks for your efforts and time.</div><div><br></div><div>I have successfully installed and tested OpenMPI. I also configured Quant Espresso and received the "Parallel environment detected successfully, configured for compilation of parallel executables" response at the end of the config process.</div><div><br></div><div>I then compiled it,but the end of a very long output read:</div><div><br></div><div><div><font class="Apple-style-span" color="#FF1E00">ld: in /usr/local/lib, can't map file, errno=22</font></div><div><font class="Apple-style-span" color="#FF1E00">collect2: ld returned 1 exit status</font></div><div><font class="Apple-style-span" color="#FF1E00">make[1]: *** [pw.x] Error 1</font></div><div><font class="Apple-style-span" color="#FF1E00">make: *** [pw] Error 2</font></div><div><br></div><div>This doesn't look good and I can't find any list of these errors in the user guide. I tried example01 and received (of course) this output:</div><div><div><font class="Apple-style-span" color="#FF1E00">ERROR: /usr/local/espresso-4.0.5/bin/pw.x not existent or not executable</font></div><div><font class="Apple-style-span" color="#FF1E00">Aborting</font></div></div></div><div><br></div><div>Any ideas?</div><div><br></div><div>cheers,</div><div>Mike</div><div><br></div><div><br></div><div><div><div>On Jun 10, 2009, at 7:05 PM, Alain Jacques wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"> <div bgcolor="#ffffff" text="#000000"> Hello Mike,<br> <br> Humm, sorry it didn't work as expected. My development platform runs OSX 10.5.7. I have compiled many working openmpi versions with the following recipe:<br> <br> export LD_LIBRARY_PATH=/opt/gcc-4.3.2/lib:$LD_LIBRARY_PATH && export PATH=/opt/gcc-4.3.2/bin:$PATH<br> <br> ./configure --prefix=/opt/openmpi-1.2.8_gcc-4.3.2_m32 --enable-static --enable-shared --disable-dependency-tracking --with-devel-headers --with-wrapper-ldflags="-Wl,-search_paths_first" CC=/opt/gcc-4.3.2/bin/gcc LDFLAGS="-L/opt/gcc-4.3.2/lib" FC=/opt/gcc-4.3.2/bin/gfortran F77=/opt/gcc-4.3.2/bin/gfortran CXX=/opt/gcc-4.3.2/bin/g++ CPP=/opt/gcc-4.3.2/bin/cpp CFLAGS="-m32 -O3 -march=native" CXXFLAGS="-m32 -O3 -march=native" FCFLAGS="-m32 -O3 -march=native" FFLAGS="-m32 -O3 -march=native"<br> <br> As you understand, my homemade gcc/gfortran lives in /opt/gcc-4.3.2/bin and I install the corresponding openmpi in /opt/openmpi-1.2.8_gcc-4.3.2_m32. Same story with openmpi up to version 1.3.2 and gcc up to 4.4.0. The -m32 flag is there to specify 32bit binaries (-m64 will build 64bit openmpi for the corresponding binaries, adapt the LDFLAGS too). I am quite convinced that the error message you receive comes from a mixture with Apple provided openmpi libs without gfortran support.<br> And when it is done, in order to compile or run mpi software, I add the path to the new openmpi binaries and libs in front with a:<br> <br> export PATH=/opt/openmpi-1.2.8_gcc-4.3.2_m32/bin:$PATH && export DYLD_LIBRARY_PATH=/opt/openmpi-1.2.8_gcc-4.3.2_m32/lib:$DYLD_LIBRARY_PATH<br> <br> i.e. I end with a PATH=/opt/openmpi-1.2.8_gcc-4.3.2_m32/bin:/opt/gcc-4.3.2/bin:xxx and DYLD_LIBRARY_PATH=/opt/openmpi-1.2.8_gcc-4.3.2_m32/lib:/opt/gcc-4.3.2:xxx where xxx is the original content of the variables.<br> <br> Kind regards,<br> <br> Alain<br> <br></div></blockquote></div><br></div></body></html>