Franck HOUSSEN
Franck HOUSSEN
No idea. I'd say : - get LAPACK and BLAS here https://icl.cs.utk.edu/lapack-for-windows/lapack ? And then, add BLAS/LAPACK libs in the linker GUI of visual studio ? - use Unix !...
possible alternative : #303
Not familiar with bsd. Just to make sure: do you use some package manager ? or do you git-clone the github repo and build from source with configure or cmake...
Don't get what you mean. When #207 and #203 are both merged, you get the same install with autotools : ``` >> ./bootstrap; ./configure --enable-icb --enable-mpi --prefix=/tmp/autotools; make all install;...
Maybe you use a "port" (I don't know what that is ) and this is buggy. If you do thing by hand, you should get something OK if you have...
BTW, the best thing would be to add a CI build for FreeBSD. Seems it's unfortunately impossible to do that with a docker-run ran from an ubuntu host provided by...
Cirrus-CI seems to allow also for windows
Intel tool chain can not be tested here : it's not open source. Intel open-sourced partially MKL so it's only possible to test linking with MKL and/or MKL-ILP64 https://github.com/opencollab/arpack-ng/blob/0a655d918d558ef97881db2760668b8d1e3b4bc1/.travis.yml#L229 As...
So it's Intel and/or MKL specific problem. Following _exactly_ https://software.intel.com/content/www/us/en/develop/tools/oneapi/components/onemkl/link-line-advisor.html may help. You may try with `cmake` too.