<div class="gmail_quote">On Sun, Feb 27, 2011 at 01:56, F R Foust <span dir="ltr"><<a href="mailto:frfoust@yahoo.com">frfoust@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div id=":107">I was trying to build petsc using MKL blas/lapack and had a small issue. I tried to point configure at the mkl directory with --with-blas-lapack-dir, but it found an installation of ATLAS already in /usr/local/lib and used that instead. </div>
</blockquote><div><br></div><div>Is that where your MKL is? If not, then this should be considered a bug, but it's probably hard to fix because /usr/local/lib must be a system path which is searched automatically.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div id=":107"> I poked around and found a fixed search order in BuildSystem/config/packages/BlasLapack.py (it tries ATLAS, AMD ACML, then MKL).<br>
<br>
Is there any way to force a specific flavor of BLAS in a flag passed to configure (I mean, so I don't have to modify BlasLapack.py, which is what I did). Or alternatively, is there a way to force the issue by using --with-blas-lapack-lib, --with-blas-lib? I wasn't able to figure out the correct incantation to include all of the stuff MKL needs to link against.</div>
</blockquote></div><div><br></div><div>You can find what is necessary here, then put it in --with-blas-lapack-lib.</div><br><div><a href="http://software.intel.com/en-us/articles/intel-mkl-link-line-advisor/">http://software.intel.com/en-us/articles/intel-mkl-link-line-advisor/</a></div>