On Sep 30, 2015, at 2:38 PM, Satish Balay <[email protected]> wrote:

On Wed, 30 Sep 2015, Jed Brown wrote:

...

Satish Balay <[email protected]> writes:

...

I think the issue was - blaslapack.py [as is currently organized] does not need or care for mkl.h. But mkl_cpardiso.py requires it. For mkl_cpardiso.py to find it - it requires the -dir - or include/lib options.

Can one use mkl_pardiso with a different BLAS/Lapack? If not, maybe --with-mkl-dir= or some such to avoid repetition of the ridonculous paths.

What you are suggesting is merge mkl_pardiso.py, mkl_pardiso.py [and mkl_spmv2.py] into a single mkl.py - and then add in the support for these features inside it.

--with-mkl-dir=LOCATION_OF_INTEL_MKL --with-mkl-pardiso=1 --with-mkl-cpardiso=1 --with-mkl-spmv2=1

No, each gets their own file but they use the blas/lapack directory as the directory to look for stuff. Barry

[or autodetect pardiso, cpardiso spmv2 etc..]

perhaps this is possible..

Satish