error loading shared libraries: libguide.so

[angeli_diego]

Hi all,
I've got the intel fortran compiler and mkl installed on a P4
The Linux OS is Kubuntu (maybe not the fittest for computational apps but...)
All installations were successful, maybe it is worthy to report that I had to use alien to convert the mkl rpm to a ".deb" package to get it installed - so I didn't use the standard install.sh script.

Once I build up my application this way:...

ifort -O3 -axN -tpp7 -pc64 -unroll -o DNSNatu main.o CommonVars.o clWorld2D.o clGrid2D.o CellTools.o clBCinters2Dpoint.o clBCIntersDiag2DPoint.o clRegion2D.o clBCSeg2D.o clBCSegment2D.o PolyTools.o PoissonTools.o GeoTools.o MathTools.o clGridDir.o clInterior2D.o clSim2D.o CommonDefs.o -L/opt/intel/mkl/8.0/lib/32/ -L/opt/intel/fc/9.0/lib/ -lmkl_lapack95 -lmkl_blas95 -lmkl_lapack -lmkl_ia32 -lguide -lpthread

without getting ANY error message, and then I launch the executable binary:....

diego@angeli-nb:~/work/DNSNatu$ ./DNSNatu

I get the following message:...

./DNSNatu: error while loading shared libraries: libguide.so: cannot open shared object file: No such file or directory

I read another similar thread on this subject and there it was suggested to add to the /etc/ld.so.conf file a line with the correct path /opt/intel/mkl/8.0/lib/32. I did it but nothing changed.
I excuse myself to bring forth the question again, but I'm really clueless about it.

Note that, two months ago, on a Suse9.3 system, same PC, all worked well.

If anyone has any suggestions, I'd be very grateful about it.

Thanks in advance.

Diego Angeli
Modena (Italy)

[TimP]

Do you have at least one of the libraries containing a libguide.so specified in LD_LIBRARY_PATH ? If you wish to use a static link against the ifort libraries, the option -i-static is available.

[angeli_diego]

yes, I had NO path in the LD_LIBRARY_PATH variable. By re-assigning the variable with the mkl path, all worked well.
Probably the package conversion made me succeed in installing the mkl library correctly, but the mkl path wasn't added automatically to the right file. Now I wonder where is this addition to be done for my current system, to make it work the best way.

Thank you very much
Best regards

Diego Angeli

[TimP]

The preferred arrangement is to link and run against the newer of the libguide versions provided with MKL and with the Intel compiler. If you will use MKL only with an Intel compiler which provides a newer libguide, you could remove libguide from the MKL installation. Otherwise, to avoid linking against an older libguide provided by MKL, you would remove the -L and -l specifications associated with MKL, instead giving the full path name of each MKL library you intend to use.
Unfortunately, these complications come about when you have differing versions of libguide on your system. Since ifort 8.0, they are intended to be upward compatible, that is, a newer libguide should work with objects compiled with earlier compilers.
Even with MKL 8.0.1, which recognizes newer CPUs such as "Yonah" core/duo and Merom/Woodcrest, the libguide does not match up with the newer one provided with ifort upgrades which recognize those CPUs.
I'm sure I will not be the only one submitting reports about this on premier.intel.com. The above discussion summarizes what I got out of doing so.