On Nov 18, 3:02 pm, "Ondrej Certik" <[EMAIL PROTECTED]> wrote:
> > * the new scipy.spkg does not build on sage.math in case you compile
> > 2.8.12 from scratch. If you take the 2.8.12 binary from sage.math it
> > does work. You are required to build the new numpy first, though. I
> > tried fixing this, but after 8 hours I have given up. Once the new
> > scipy failed even installing the old numpy doesn't make the old scipy
> > compile. I ended up building the sources completely from scratch 4 or
> > 5 times - imagine my happiness level going down rapidly.
>
> Where is the problem exactly? Is it the scipy 0.6.0? Those build
> issues are annoing.
> I don't have experience with numpy, but if you need help with scipy, I
> am one of the Debian maintainers of it.
It seems that it fails to detect a proper BLAS. But since the current
scipy works there is no urgent need to update. Josh is probably the
better person to discuss this with, he was able to reproduce this
after also building 2.8.12 from source. #1198 has more info on that.
There are certainly issues in the spkg-install, but shouldn't we use a
proper naming scheme for the spkg, i.e. more than just the release
date?
> > * Ondrey's sympy patch touches coerce.pyx and that part of the patch
> > causes segfaults all over the map, so I backed it out of alpha0 for
> > now.
>
> More details in:
>
> http://sagetrac.org/sage_trac/ticket/1189
>
I also added some comments after you.
> Ondrej
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
