Was there ever a fix/workaround introduced for this? I'm using 2.3.3p13 and I'm having trouble getting the config to recognize mkl 10.0.3.020.
Thanks, Paul Barry Smith wrote: > > Could you email to petsc-maint at mcs.anl.gov ALL the messages as to > what goes wrong with > our current linking so we can fix it? > > Thanks > > Barry > > On Jun 18, 2008, at 3:32 PM, Randall Mackie wrote: > >> We've upgraded Intel MKL to version 10.0, but in this version, Intel has >> changed how libraries are suppose to be linked. For example, the >> libmkl_lapack.a >> is a dummy library, but that's what the PETSc configure script looks >> for. >> >> The documentation says, for example, to compile LAPACK in the static >> case, >> use libmkl_lapack.a libmkl_em64t.a >> >> and in the layered pure case to use >> libmkl_intel_lp64.a libmkl_intel_thread.a libmkl_core.a >> >> However, the PETSC configuration wants -lmkl_lapack -lmkl -lguide >> -lpthread >> >> Any suggestions are appreciated. >> >> Randy >> >
