Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#58123 - [octave] octave warns that the eigs function does not work properly
Attached to Project:
Community Packages
Opened by Alexander F. Rødseth (xyproto) - Thursday, 05 April 2018, 11:18 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 03 September 2018, 15:02 GMT
Opened by Alexander F. Rødseth (xyproto) - Thursday, 05 April 2018, 11:18 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 03 September 2018, 15:02 GMT
|
DetailsDescription:
I got a very informative e-mail from Saleh Bawazeer, letting me know that the current version of arpack has an issue with the eigs function, that the next (unreleased) version has fixed. This is with octave and arpack 3.5.0: Command/steps to reproduce: ./bootstrap && rm -r .build && mkdir .build && cd .build && ../configure --prefix=/home/sas/octave/4.2.1/ --without-osmesa Output: WARNING: ARPACK library found, but does not seem to work properly; disabling eigs function Tests fail: scripts/sparse/eigs.m ....................................... PASS 6/6 (missing feature) SKIP 173 scripts/sparse/gmres.m ...................................... PASS 16/16 ..... PASS 14736 FAIL 3 XFAIL (reported bug) 31 XFAIL (expected failure) 6 SKIP (missing feature) 217 SKIP (run-time condition) 12 With arpack 3.6.0 this does not happen, but 3.6.0 has not been released yet. The arpack package has now been updated, so if octave is rebuilt, this is likely to be fixed. |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Monday, 03 September 2018, 15:02 GMT
Reason for closing: Fixed
Additional comments about closing: presumably fixed by 4.4.1
Monday, 03 September 2018, 15:02 GMT
Reason for closing: Fixed
Additional comments about closing: presumably fixed by 4.4.1
Comment by Alexander F. Rødseth (xyproto) -
Thursday, 05 April 2018, 11:40 GMT
Updated arpack to use the latest commit while waiting for the 3.6.0 release. This should fix the issue in arpack.