[vsipl++] sourceryvsipl++-2.2 and Intel MKL version 10.2.5.035

Thu May 13 20:47:31 UTC 2010

Thanks for the information. I do have a few more questions.

(1)

I do not have a copy of MKL 8.x. Are you saying the alternative method
will allow configure to complete successfully?

In the intel directory (/home/developer/intel/mkl/10.2.5.035/lib/64 ) I
have a shared object named libmkl_lapack.so so

I am not quite sure what I would change the line you specified
(LIBS="$keep_LIBS -lmkl_lapack -lmkl -lguide -lpthread ) to be

Since the library requested is the one that I already have.

I also do not see an available library named anything close to ( -lmkl
which translates to libmkl.so ).  Perhaps I should use the one named
libmkl_core.so that I would translate to lmkl_core instead?

Here is the list of available libraries:

libguide.a                      libmkl_blacs_sgimpt_lp64.a
libmkl_intel_ilp64.a       libmkl_scalapack_lp64.a

libguide.so                     libmkl_blas95_ilp64.a
libmkl_intel_ilp64.so      libmkl_scalapack_lp64.so

libiomp5.a                      libmkl_blas95_lp64.a
libmkl_intel_lp64.a        libmkl_sequential.a

libiomp5.so                     libmkl_cdft_core.a
libmkl_intel_lp64.so       libmkl_sequential.so

libmkl_blacs_ilp64.a            libmkl_core.a
libmkl_intel_sp2dp.a       libmkl_solver_ilp64.a

libmkl_blacs_intelmpi_ilp64.a   libmkl_core.so
libmkl_intel_sp2dp.so      libmkl_solver_ilp64_sequential.a

libmkl_blacs_intelmpi_ilp64.so  libmkl_gf_ilp64.a
libmkl_intel_thread.a      libmkl_solver_lp64.a

libmkl_blacs_intelmpi_lp64.a    libmkl_gf_ilp64.so
libmkl_intel_thread.so     libmkl_solver_lp64_sequential.a

libmkl_blacs_intelmpi_lp64.so   libmkl_gf_lp64.a
libmkl_lapack95_ilp64.a    libmkl_vml_i2p.so

libmkl_blacs_lp64.a             libmkl_gf_lp64.so
libmkl_lapack95_lp64.a     locale

libmkl_blacs_openmpi_ilp64.a    libmkl_gnu_thread.a
libmkl_lapack.so

libmkl_blacs_openmpi_lp64.a     libmkl_gnu_thread.so
libmkl_scalapack_ilp64.a

libmkl_blacs_sgimpt_ilp64.a     libmkl_i2p.so
libmkl_scalapack_ilp64.so

(2)

Can you also state, if you know, the difference between the intel
directories /home/developer/intel/mkl/10.2.5.035 and

/home/developer/intel/cmkl/10.2.5.035.  

(3)  

If I am going to use MKL I presume I would NOT want to also include
flags for:

--with-fftw3 and --with-lapack=atlas,
--with-atlas-prefix=/home/developer/local

I didn't do so in my configuration attempt because I presume it is not
needed.

(4)

Is Intel's IPP also needed if I use the MKL?  I would presume you can
use one without the other but perhaps not.

Thanks in advance for the assistance,

Bill

-----Original Message-----
From: Brooks Moses [mailto:brooks at codesourcery.com] 
Sent: Thursday, May 13, 2010 4:27 PM
To: Cassanova, Bill
Cc: vsipl++ at codesourcery.com
Subject: Re: [vsipl++] sourceryvsipl++-2.2 and Intel MKL version
10.2.5.035

Hello, Bill -

Yes, MKL changed the set of libraries to link to between versions 8.x

and the current 10.x version, and so the configure script in the current

versions of Sourcery VSIPL++ does not correctly recognize them.

We'll be adding support for MKL version 10.x in our next set of releases

this fall.

Meanwhile, if you do have a copy of MKL version 8.x available, you can

build the library against that, and then build your VSIPL++ applications

against MKL 10.x (with adjusted linker command line as appropriate).

The MKL API is sufficiently stable for this to work correctly, and with

static linking your applications will end up only using the code from

the MKL 10.x library.

(Alternately, if you look in the m4/lapack.m4 configure file, at about

line 193 you'll see the set of libraries checked for MKL; those are

currently "-lmkl_lapack -lmkl -lguide -lpthread".  You should be able to

hack those to point to the current appropriate set of MKL libraries.)

Let me know if that works for you, or if you have any other questions!

Thanks,

- Brooks

Cassanova, Bill wrote, at 5/13/2010 12:42 PM:

> Hi everyone,

> 

> Just wondering if anyone has been able to get vsipl++ to properly
configure with 

> MKL version 10.2.5.035.

> 

> I have made multiple attempts:

> 

> ./configure --prefix=/home/developer/local --enable-shared-libs 

> --enable-fft=fftw3 --enable-parallel=probe 

> --with-fftw3-prefix=/home/developer/local 

> --with-mkl-prefix=/home/developer/intel/mkl --with-mkl-arch=64

> 

> ./configure --prefix=/home/developer/local --enable-shared-libs 

> --enable-fft=fftw3 --enable-parallel=probe 

> --with-fftw3-prefix=/home/developer/local 

> --with-mkl-prefix=/home/developer/intel/mkl/10.2.5.035
--with-mkl-arch=64

> 

> ./configure --prefix=/home/developer/local --enable-shared-libs 

> --enable-fft=fftw3 --enable-parallel=probe 

> --with-fftw3-prefix=/home/developer/local 

> --with-mkl-prefix=/home/developer/intel/cmkl --with-mkl-arch=64

> 

> ./configure --prefix=/home/developer/local --enable-shared-libs 

> --enable-fft=fftw3 --enable-parallel=probe 

> --with-fftw3-prefix=/home/developer/local 

> --with-mkl-prefix=/home/developer/intel/cmkl/10.2.5.035
--with-mkl-arch=64

> 

> All with the same error:

> 

> Using 64 for MKL architecture directory

> 

> Searching for LAPACK packages: mkl7 mkl5

> 

> checking for LAPACK/MKL 7.x or 8.x library... not found

> 

> checking for LAPACK/MKL 5.x library... not found

> 

> configure: error: LAPACK enabled but no library found

> 

> My presumption is only MKL versions 7.x and 8.x are supported? If this
the case 

> are there any plans to support MKL version 10.x?

> 

> Thanks,

> 

> Bill

> 

-- 

Brooks Moses

CodeSourcery

brooks at codesourcery.com

650-331-3385 x726

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sourcerytools.com/pipermail/vsipl++/attachments/20100513/15188e63/attachment.html>