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#10186 - [python-scipy 0.6.0-1] LAPACK Fortran problems
Attached to Project:
Community Packages
Opened by Przemyslaw K. (CoolGenie) - Monday, 14 April 2008, 05:43 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 18 May 2008, 22:15 GMT
Opened by Przemyslaw K. (CoolGenie) - Monday, 14 April 2008, 05:43 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 18 May 2008, 22:15 GMT
|
DetailsDescription:
Problems with libgfortran.so.2 -- this is an issue with gcc-4.3.0: >>> from scipy import * Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.5/site-packages/scipy/linalg/__init__.py", line 8, in <module> from basic import * File "/usr/lib/python2.5/site-packages/scipy/linalg/basic.py", line 17, in <module> from lapack import get_lapack_funcs File "/usr/lib/python2.5/site-packages/scipy/linalg/lapack.py", line 17, in <module> from scipy.linalg import flapack ImportError: libgfortran.so.2: cannot open shared object file: No such file or directory |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Sunday, 18 May 2008, 22:15 GMT
Reason for closing: Fixed
Additional comments about closing: fixed by me
Sunday, 18 May 2008, 22:15 GMT
Reason for closing: Fixed
Additional comments about closing: fixed by me

Just came to my mind -- maybe it's an issue with lapack and not with scipy...

it's an issue with python-scipy. It needs to be rebuilt against gcc 4.3.0