Hi Ralph,

If I did this right (NEVER a good bet :-) ), it didn't work...

Using last night's master nightly, openmpi-dev-1515-gc869490.tar.bz2, I built with the same script as yesterday, but removing the LDFLAGS=-Wl, stuff:

$ ./configure --prefix=/home/ariebs/mic/mpi-nightly CC="icc -mmic" CXX="icpc -mmic" \
  --build=x86_64-unknown-linux-gnu --host=x86_64-k1om-linux \
   AR=x86_64-k1om-linux-ar RANLIB=x86_64-k1om-linux-ranlib LD=x86_64-k1om-linux-ld \
   --enable-mpirun-prefix-by-default --disable-io-romio --disable-mpi-fortran \
   --enable-debug --enable-mca-no-build=btl-usnic,btl-openib,common-verbs,oob-ud
$ make
$ make install
 ...
make[1]: Leaving directory `/home/ariebs/mic/openmpi-dev-1515-gc869490/test'
make[1]: Entering directory `/home/ariebs/mic/openmpi-dev-1515-gc869490'
make[2]: Entering directory `/home/ariebs/mic/openmpi-dev-1515-gc869490'
make  install-exec-hook
make[3]: Entering directory `/home/ariebs/mic/openmpi-dev-1515-gc869490'
make[3]: ./config/find_common_syms: Command not found
make[3]: [install-exec-hook] Error 127 (ignored)
make[3]: Leaving directory `/home/ariebs/mic/openmpi-dev-1515-gc869490'
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/ariebs/mic/openmpi-dev-1515-gc869490'
make[1]: Leaving directory `/home/ariebs/mic/openmpi-dev-1515-gc869490'
$

But it seems to finish the install.

I then tried to run, adding the new mca arguments:

$  shmemrun -x SHMEM_SYMMETRIC_HEAP_SIZE=1M -mca plm_rsh_pass_path $PATH -mca plm_rsh_pass_libpath $MIC_LD_LIBRARY_PATH -H mic0,mic1 -n 2 ./mic.out
/home/ariebs/mic/mpi-nightly/bin/orted: error while loading shared libraries: libimf.so: cannot open shared object file: No such file or directory
 ...
$ echo $MIC_LD_LIBRARY_PATH
/opt/intel/15.0/composer_xe_2015.2.164/compiler/lib/mic:/opt/intel/15.0/composer_xe_2015.2.164/mpirt/lib/mic:/opt/intel/mic/coi/device-linux-release/lib:/opt/intel/mic/myo/lib:/opt/intel/15.0/composer_xe_2015.2.164/ipp/lib/lib/mic:/opt/intel/mic/coi/device-linux-release/lib:/opt/intel/mic/myo/lib:/opt/intel/15.0/composer_xe_2015.2.164/compiler/lib/mic:/opt/intel/15.0/composer_xe_2015.2.164/mkl/lib/mic:/opt/intel/15.0/composer_xe_2015.2.164/tbb/lib/mic
$ ls /opt/intel/15.0/composer_xe_2015.2.164/compiler/lib/mic/libimf.*
/opt/intel/15.0/composer_xe_2015.2.164/compiler/lib/mic/libimf.a
/opt/intel/15.0/composer_xe_2015.2.164/compiler/lib/mic/libimf.so
$


On 04/16/2015 07:22 AM, Ralph Castain wrote:
FWIW: I just added (last night) a pair of new MCA params for this purpose:

plm_rsh_pass_path <foo>   prepends the designated path to the remote shell's PATH prior to executing orted
plm_rsh_pass_libpath <foo>  same thing for LD_LIBRARY_PATH

I believe that will resolve the problem for Andy regardless of compiler used. In the master now, waiting for someone to verify it before adding to 1.8.5. Sadly, I am away from any cluster for the rest of this week, so I'd welcome anyone having a chance to test it.


On Thu, Apr 16, 2015 at 2:57 AM, Thomas Jahns <ja...@dkrz.de> wrote:
Hello,

On Apr 15, 2015, at 02:11 , Gilles Gouaillardet wrote:
what about reconfiguring Open MPI with LDFLAGS="-Wl,-rpath,/opt/intel/15.0/composer_xe_2015.2.164/compiler/lib/mic" ?

IIRC, an other option is : LDFLAGS="-static-intel"

let me first state that I have no experience developing for MIC. But regarding the Intel runtime libraries, the only sane option in my opinion is to use the icc.cfg/ifort.cfg/icpc.cfg files that get put in the same directory as the corresponding compiler binaries and add a line like

-Wl,-rpath,/path/to/composerxe/lib/intel??

to that file.

Regards, Thomas
-- 
Thomas Jahns
DKRZ GmbH, Department: Application software

Deutsches Klimarechenzentrum
Bundesstraße 45a
D-20146 Hamburg

Email: Thomas Jahns <ja...@dkrz.de>




_______________________________________________
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: http://www.open-mpi.org/community/lists/users/2015/04/26745.php



_______________________________________________
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: http://www.open-mpi.org/community/lists/users/2015/04/26746.php


Reply via email to