Hi Satish,<br><br>I compiled PETSC with the following options:<br><br>./configure PETSC_ARCH=linux-intel-opt --with-fortran-kernels=generic --with-blas-lapack-dir<br>=/opt/intel/mkl/<a href="http://10.0.3.020/lib/64">10.0.3.020/lib/64</a> --with-scalar-type=complex --with-debugging=0<br>
<br>PETSc compiled just fine, but when I tried to compile my application, or run the tests<br>within PETSC, it bombed out looking for the MKL libraries like:<br><br><br>mpif90 -O -o d3inv_DA_1_1_4_petsc ... ,-rpath,/opt/intel/mkl/<a href="http://10.0.3.020/lib/64">10.0.3.020/lib/64</a> -L/opt/intel/mkl/<a href="http://10.0.3.020/lib/64">10.0.3.020/lib/64</a> -lmkl_lapack -lmkl -lguide -lpthread -lPEPCF9r/lib64 -L/usr/mpi/intel/mvapich-1.0.1/lib/shared -L/usr/mpi/intel/mvapich-1.0.1/lib -ldl -lmpich -libverbs -libumad -libcommon -lpthread -lrt -L/opt/intel/mkl/<a href="http://10.0.3.020/libopt/intel/mkl/10.0.3.020/lib/em64t">10.0.3.020/libopt/intel/mkl/10.0.3.020/lib/em64t</a> ......<br>
<br>ld: skipping incompatible /opt/intel/mkl/<a href="http://10.0.3.020/lib/64/libmkl_lapack.so">10.0.3.020/lib/64/libmkl_lapack.so</a> when searching for -lmkl_lapack<br>etc.<br><br>I'll try Paul's method of specifying the exact libraries to be included. If you want, I can<br>
still send you the configure log.<br><br>Randy<br><br><div class="gmail_quote">On Tue, Feb 3, 2009 at 3:25 PM, Satish Balay <span dir="ltr"><<a href="mailto:balay@mcs.anl.gov">balay@mcs.anl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I just successfully compiled petsc-dev [which is almost same as<br>
petsc-3.0.0-p3] & MLK successfully with both intel & gnu compilers.<br>
<br>
./configure --with-blas-lapack-dir=/gfs/software/software/intel/compilersuite/10.1/mkl/10.0.011 --with-mpi=0 PETSC_ARCH=linux-mkl<br>
<br>
<br>
./configure --with-blas-lapack-dir=/gfs/software/software/intel/compilersuite/10.1/mkl/10.0.011 --with-mpi=0 PETSC_ARCH=linux-icc-mkl CC=icc FC=ifort<br>
<br>
What problems are you encountering? Send configure.log to petsc-maint..<br>
<font color="#888888"><br>
Satish<br>
</font><div><div></div><div class="Wj3C7c"><br>
On Tue, 3 Feb 2009, Randall Mackie wrote:<br>
<br>
> Paul,<br>
><br>
> Have you tried this with Petsc 3.0.0? I just tried to compile it using<br>
> MKL 10.0.3.020, and I am having the same issue you specified below, in that<br>
> Petsc is looking for -lmkl_lapack -lmkl -lguide etc and the compilation<br>
> doesn't work.<br>
><br>
> Randy<br>
><br>
><br>
><br>
><br>
> Paul T. Bauman wrote:<br>
> > Sorry this took so long to get around to doing. So it turns out that there's<br>
> > a newer version of 2.3.3p13 posted at the PETSc ftp server. This worked<br>
> > flawlessly with the new MKL. I guess it got fixed and checked-in, but not<br>
> > under a new patch?<br>
> ><br>
> > Thanks,<br>
> ><br>
> > Paul<br>
> ><br>
> > Barry Smith wrote:<br>
> > ><br>
> > > Please send the configure.log to <a href="mailto:petsc-maint@mcs.anl.gov">petsc-maint@mcs.anl.gov</a><br>
> > ><br>
> > > Barry<br>
> > ><br>
> > > On Aug 15, 2008, at 1:39 PM, Paul T. Bauman wrote:<br>
> > ><br>
> > > > Was there ever a fix/workaround introduced for this? I'm using 2.3.3p13<br>
> > > > and I'm having trouble getting the config to recognize mkl 10.0.3.020.<br>
> > > ><br>
> > > > Thanks,<br>
> > > ><br>
> > > > Paul<br>
> > > ><br>
> > > > Barry Smith wrote:<br>
> > > > ><br>
> > > > > Could you email to <a href="mailto:petsc-maint@mcs.anl.gov">petsc-maint@mcs.anl.gov</a> ALL the messages as to<br>
> > > > > what goes wrong with<br>
> > > > > our current linking so we can fix it?<br>
> > > > ><br>
> > > > > Thanks<br>
> > > > ><br>
> > > > > Barry<br>
> > > > ><br>
> > > > > On Jun 18, 2008, at 3:32 PM, Randall Mackie wrote:<br>
> > > > ><br>
> > > > > > We've upgraded Intel MKL to version 10.0, but in this version, Intel<br>
> > > > > > has<br>
> > > > > > changed how libraries are suppose to be linked. For example, the<br>
> > > > > > libmkl_lapack.a<br>
> > > > > > is a dummy library, but that's what the PETSc configure script looks<br>
> > > > > > for.<br>
> > > > > ><br>
> > > > > > The documentation says, for example, to compile LAPACK in the static<br>
> > > > > > case,<br>
> > > > > > use libmkl_lapack.a libmkl_em64t.a<br>
> > > > > ><br>
> > > > > > and in the layered pure case to use<br>
> > > > > > libmkl_intel_lp64.a libmkl_intel_thread.a libmkl_core.a<br>
> > > > > ><br>
> > > > > > However, the PETSC configuration wants -lmkl_lapack -lmkl -lguide<br>
> > > > > > -lpthread<br>
> > > > > ><br>
> > > > > > Any suggestions are appreciated.<br>
> > > > > ><br>
> > > > > > Randy<br>
> > > > > ><br>
> > > > ><br>
> > > ><br>
> > ><br>
> > ><br>
> ><br>
> ><br>
><br>
><br>
<br>
</div></div></blockquote></div><br>