Franck HOUSSEN
Franck HOUSSEN
@manavbhatia : did you try with slepc ? slepc + lapack should be OK (as you tried directly with lapack). if slepc + arpack is OK, it means the way...
@manavbhatia : so all is OK now if I got it well ? What about adding version check for lapack (> 3.6.1 ?) in cmake/autotools ? personal opinion: since the...
> I support the addition of such a utility. I think it will be great, so that users don't have to write and debug their own reverse-communication code. :+1: ......
> So, I would vote for both eigen and petsc. petsc: cmake file is not provided, pc file is provided (if configured) but not shipped by .deb package => impossible...
If I find some free time, I can try to prototype something...
Would say you need lapack 3 (dlahqr used instead of deprecated dlaqrb) and this fix: ``` $ git diff diff --git a/VISUAL_STUDIO/arpack-ng_exports.def b/VISUAL_STUDIO/arpack-ng_exports.def index 2129b28..ab447a5 100644 --- a/VISUAL_STUDIO/arpack-ng_exports.def +++ b/VISUAL_STUDIO/arpack-ng_exports.def...
Please PR the fix. Arpack needs blas / lapack : you'll need to add them in your paths according to your IDE (no windows, can't help). Not sure to understand...
Give a try to cmake (or autotools) on windows ? You'll need to build blas and lapack with cmake, then, to build arpack (which needs blas / lapack) with cmake...
@sylvestre : https://docs.travis-ci.com/user/reference/windows/
Even if you would, you'll need to wget and build blas / lapack (I guess you don't want that)