Franck HOUSSEN
Franck HOUSSEN
These tests are meant to be run sequentially: restart infos are stored into a file that do not support concurrent access
> Ok. Could only those tests be run sequentially? Sure > **make** has [special markers](https://www.gnu.org/software/make/manual/html_node/Parallel-Disable.html) for targets that require sequential handling. No idea how
Does your BLAS/LAPACK supports LTO? Feel free to PR a fix if you find one.
Yes, sure!
Not sure if I could help. What are the options of the configure? Does your lapack switched to lp64 or ilp64? Did your env changed? Can't tell!
> Should still be the same one included with 32-bit integer OpenBLAS arpack depends on BLAS / LAPACK implementations (netlib, mkl, ...): you may try with an older version of...
Do you export these variables? https://github.com/opencollab/arpack-ng/blob/9431fd5ea66a00e696695ecbc5c6a02e1ebabca7/.github/workflows/jobs.yml#L184-L190
In `-O0` does `-Wall -Werror` give some hints? Does adding `-ffpe-trap=zero,overflow,underflow,invalid -fcheck=all` give more info? You may hit overflow here https://github.com/opencollab/arpack-ng/blob/9431fd5ea66a00e696695ecbc5c6a02e1ebabca7/TESTS/dnsimp.f#L448 or https://github.com/opencollab/arpack-ng/blob/9431fd5ea66a00e696695ecbc5c6a02e1ebabca7/TESTS/dnsimp.f#L467 (potential divide by zero ?)
Nope. Feel free to propose a PR (with CI).
Maybe adding `conan` to handle dependencies for `cmake`?