linking with openmp static lib

linking with openmp static lib

Portrait de Terry Gerald

A sample program:

program quest

#ifdef _VEM_OMP

   use omp_lib

#endif

#ifdef _VEM_OMP

  write(*,*)  "num procs:", omp_get_num_procs()

#endif

  write(*,*) "Finished"

end

 

Compile & link with:

>ifort -fpp -D_VEM_OMP -openmp-link static quest.f90 -o quest -L/opt/intel/Compiler/11.0/081/lib/intel64 -liomp5

run with:

>./quest

Response:

>./quest: error while loading shared libraries:libiomp5.so: cannot open shared object file: No such file

 

Question: Why is it trying to find and load a dynamic lib when I told it to do a static link?

 

 

3 posts / 0 nouveau(x)
Dernière contribution
Reportez-vous à notre Notice d'optimisation pour plus d'informations sur les choix et l'optimisation des performances dans les produits logiciels Intel.
Portrait de IanH

Because you inadvertently specified the dynamic library by putting the -liomp5 option in the command line. By default the linker first searches for the shared variant of any libraries that you specify. You need -Bstatic before that -l option if you want the linker to search for the static variant.

But why do you have that -l option, or the -L option there at all? The compiler driver manages that sort of stuff for you.

Portrait de Annalee (Intel)

There is no longer a static version of the OpenMP library, so the compiler will always use the dynamic OpenMP library when you use OpenMP. This is the case even if you compile you specify static.

Connectez-vous pour laisser un commentaire.