[SciPy-dev] install problems, SUSE, check_heev

Arnd Baecker arnd.baecker at web.de
Thu Feb 3 07:07:02 CST 2005


On Thu, 3 Feb 2005, Nils Wagner wrote:

> [...]

>  Hi Arnd,
>
> I cannot reproduce your errors
> check_nils (scipy.linalg.matfuncs.test_matfuncs.test_logm)Result may be inaccurate, approximate err = 4.39192767776e-09
>  ... ok
> check_defective1 (scipy.linalg.matfuncs.test_matfuncs.test_signm) ... ok
> check_defective2 (scipy.linalg.matfuncs.test_matfuncs.test_signm) ... ok
> check_defective3 (scipy.linalg.matfuncs.test_matfuncs.test_signm) ... ok
> check_nils (scipy.linalg.matfuncs.test_matfuncs.test_signm) ... ok
>
>
> >>> scipy.__version__
> '0.3.3_302.4564'
>
> >>> Numeric.__version__
> '23.7'
>
> f2py -v
> 2.45.241_1926
>
> Python 2.3.3 (#1, Apr  6 2004, 01:47:39)
> [GCC 3.3.3 (SuSE Linux)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.

Very interesting, I have the same version, apart from
- python 2.3.4
- gcc version 3.3.4 (pre 3.3.5 20040809)
The machine is an  AMD Athlon(TM) XP 2200+

Is it the right thinking that I need to solve this problem
first before proceeding to the full ATLAS?

BTW (Pearu), I did not change LAPACK/make.inc
in this case (because I used the source code variant) - is it right
that scipy takes care of the flags in this case?

((Or should I better compile LAPACK directly,
as described in scipy's INSTALL.txt
       cd /path/to/src/LAPACK
       make lapacklib    # On 400MHz PII it takes about 15min.
and play around with the flags as you described
in your previous mail?
))

Many thanks,

Arnd




More information about the Scipy-dev mailing list