And also somehow hedge against library name changes [or new arches?]
Yeah - its python script - and can do such things [as long as there
are no -ve affects].
[Its already way too complicated - and probably needs
purging/reorganizing]
Satish
On Wed, 21 Dec 2016, Jeff Hammond wrote:
> Is Petsc b
Is Petsc build system not capable of running "find" on $MKLROOT as a hedge
against subdirectories reorganization?
At least with Intel compilers, "-mkl" is the easy button unless you're
trying to get threaded BLAS/LAPACK with ScaLAPACK.
Jeff
On Wed, Dec 21, 2016 at 7:37 AM Pierre Jolivet
wrote:
On Wed, 21 Dec 2016 09:17:33 -0600, Satish Balay wrote:
I've added $MKLROOT/lib/ to search path for MKL. Thanks for the
report.
https://bitbucket.org/petsc/petsc/commits/7fe016461159234c29eaa106eb46d0bf81683f36
Thanks.
Wrt libiomp5.dylib - its an intel compiler library - so its found
when
Ok from https://clang-omp.github.io/ "OpenMP 3.1 is fully supported in
clang/llvm 3.7"
With my linux clang-3.9.0 install I see:
balay@asterix /home/balay/soft/clang+llvm-3.9.0-x86_64-fedora23/lib
$ ls -lt *omp*
-rwxr-xr-x. 1 balay balay 763736 Sep 1 16:05 libomp.so*
lrwxrwxrwx. 1 balay balay
I've added $MKLROOT/lib/ to search path for MKL. Thanks for the report.
https://bitbucket.org/petsc/petsc/commits/7fe016461159234c29eaa106eb46d0bf81683f36
Wrt libiomp5.dylib - its an intel compiler library - so its found when
using icc,icpc [as you describe below].
I guess it doesn't work when b
Hello,
There are some issues when using (most recent versions of) the MKL on macOS:
1) the correct path to libmkl_*.dylib is now $MKLROOT/lib/, but this is not
taken into account by the build system
diff --git a/config/BuildSystem/config/packages/BlasLapack.py
b/config/BuildSystem/config/package