I should have said that also source the the fortran compilervars.sh as suggested by Kevin. Steve Steven C. Pieper, Senior Physicist Emeritus: [email protected] Argonne National Laboratory, Physics Division, Bldg. 203, Argonne, IL 60439 Phone: 630-252-4232 Fax -6008 Secretary, Debra Beres, -4100 http://www.phy.anl.gov/theory/staff/scp.html On 10/18/2016 09:45 AM, Harms, Kevin wrote:

Tom,

the last one using ‘-static-intel’ statically links the Intel libraries thus you don’t have any issue loading dynamic libraries. As for your first item, it appears the mpivars.sh script only provides the MPI libraries and does not add the path for the Fortran runtime libraries. You will need to add sourcing of the compiler libraries as well:

source /soft/compilers/intel/compilers_and_libraries/linux/bin/compilervars.sh intel64 mpirun -f $COBALT_NODEFILE -ppn 2 ./toys

It looks like the compilervars.sh adds all the libraries including MPI.

kevin

-----Original Message----- From:<[email protected]> on behalf of Tom LeCompte<[email protected]> Date: Tuesday, October 18, 2016 at 9:01 AM To: "[email protected]"<[email protected]> Subject: [JLSE-Intel-NDA] Fortran and shared libraries

Hi everyone-

I already have a workaround, but I am puzzled as to why I need one.

If I compile with:

mpiifort -O3 -xMIC_AVX512 -mcmodel medium -shared-intel -o toys mt19937.o toys.f

and run with

source /soft/compilers/intel/compilers_and_libraries/linux/mpi/bin64/mpivars.sh mpirun -f $COBALT_NODEFILE -ppn 2 ./toys

I get the error (twice)

./toys: error while loading shared libraries: libifport.so.5: cannot open shared object file: No such file or directory

This persists when I put /soft/compilers/intel_beta/compilers_and_libraries_2017.0.042/linux/compiler/lib/intel64_lin_mic in my LD_LIBRARY_PATH, and even when I copy libifport.so.5 into the run area and put the run area in my LD_LIBRARY_PATH. Echoing $LD_LIBRARY_PATH shows that this "took".

If I instead compile with:

mpiifort -O3 -xMIC_AVX512 -static-intel -o toys mt19937.o toys.f

It runs perfectly.

Any ideas?

Cheers,

Tom

_______________________________________________ Intel-nda mailing list [email protected] https://lists.jlse.anl.gov/mailman/listinfo/intel-nda

_______________________________________________ Intel-nda mailing list [email protected] https://lists.jlse.anl.gov/mailman/listinfo/intel-nda