Franck HOUSSEN
Franck HOUSSEN
@wztzjhn: do not use `INTERFACE64=1` ! Running with MPI on any distro _without_ `INTERFACE64` and any LP64 blas/lapack (netlib, MKL, ...) should be OK. :) Support for ILP64 arpack was...
If #372 runs OK (green CI), can you kill [e2f0483](https://github.com/opencollab/arpack-ng/pull/371/commits/e2f04839b00a6dc5a19028f500b5fd1a931d9b7f) and rebase on top of it? > what will be the use case of parallel arpack? In my past experience,...
>1. https://github.com/opencollab/arpack-ng/pull/372 becomes green and is merged into master. Yes. >2. I add a new branch and cherry pick everything except that bug fix. Simply `git rebase -i master` and...
Can you rebase? (1-change-1-commit if possible: easier to review)
> for macos it will be much faster to cache the dependencies in CI. Sure. Caching was used with (old) travis-ci but not with (new) github-actions. No time to look...
> Should le line ... be replaced ... Sounds right. PR a fix if possible (CI down at the time - hopefully back up soon...)
@yurivict : `*arpack.h*` are installed only if you `./configure --enable-icb`. Without `--enable-icb`, arpack-ng is pure fortran (means no .h/hpp)
@teamblubee : didn't even know about flang ! :D Did you try `FCFLAGS="-c" cmake -DICB=ON ..; make`
Did you try `CMAKE_Fortran_FLAGS="-c" cmake ..; make` and / or add "-c" with ccmake ?
@teamblubee : sometimes with cmake you need to ` rm -fr * ` the build directory !... Did you try. Anyway, if configure is OK, that's good as you have...