[petsc-dev] [petsc-users] mkl-cpardiso configuration

[Jose David Bermeol]

Exactly
----- Original Message -----
From: "Barry Smith" <bsmith at mcs.anl.gov>
To: "Matthew Knepley" <knepley at gmail.com>
Cc: "Jose David Bermeol" <jbermeol at purdue.edu>, petsc-users at mcs.anl.gov, "For users of the development version of PETSc" <petsc-dev at mcs.anl.gov>
Sent: Sunday, October 6, 2013 9:49:59 PM
Subject: Re: [petsc-dev] [petsc-users] mkl-cpardiso configuration


   Because he is using other stuff in mkl besides blas/lapack!

On Oct 6, 2013, at 8:43 PM, Matthew Knepley <knepley at gmail.com> wrote:

> On Sun, Oct 6, 2013 at 8:04 PM, Jose David Bermeol <jbermeol at purdue.edu> wrote:
> Hi, one question about how to configure a new package, intel people suggest to compile mkl-cpardiso using the following flags for the linker:
> 
> -Wl,--start-group -L$(MKL_PATH)/lib/intel64/ -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_core -Wl,--end-group -lpthread -lm -liomp5
> 
> Now I want to be able to do this just using the flag --with-mkl-dir=$(MKL_PATH) during Petsc configuration. I've been trying to modify my mkl.py file to achieve this, however your configuration system is a little bit complex, so if you code give some guidelines to achieve this or files to look how to do it would be great.

   Make a pull request with all your current stuff and we can look at how you've organized it and make suggestions. Otherwise it is too much email guess work with incomplete information.

   Barry

> 
> Is there a reason you do not want to use --with-blas-lapack-lib?
> 
>   Thanks,
> 
>     Matt
>  
> Thanks
> 
> 
> 
> -- 
> What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.
> -- Norbert Wiener