--enable-lapack flag problems

[azrael417]

It seems that the configure flag --enable-lapack just checks if liblapack is there. However, it would be good if it also checks if MKL is there and continue if this is the case. Maybe by test-compiling a small file which makes a lapack call with and without trailing underscores and if one of it succeeds, just continue.

[aportelli]

Hi. I am not so keen on going down the road of testing platform specific libraries like the MKL. Especially that the MKL can be configured linked in numerous different ways. However what I can do (and have already done with other libraries) is to add an option --with-lapack-name= to allow to change the name of lapack (e.g. to mkl_core). I'll look into that.

[paboyle]

We also need to be able to distinguish between MKL fftw wrappers and fftw itself in the build selection.

[aportelli]

Hi Peter, yes I will set all that clean when I will have my workstation with all the Intel software

[aportelli]

Hi Thorsten,

I have been trying to change all kind of things in the build system to address automatically some of the issues you have been filling. Could you please help me check that everything is ok?
Could you please check out our release candidate branch release/v.0.6.0 and follow the instructions in the updated README file and let me know if Grid configures and compiles fine without you needing to tweak any extra environment variables?

[aportelli]

Hi again Thorsten.

We are trying to close issues related to v0.6 in order to release. Could you please confirm that this issue is solved for you?

[azrael417]

Hi Antonin, I will come back to that today, sorry for the delay.

Am 04.11.2016 um 06:56 schrieb Antonin Portelli notifications@github.com:

Hi again Thorsten.

We are trying to close issues related to v0.6 in order to release. Could you please confirm that this issue is solved for you?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.