#9808: Upgrade numpy to 1.5.0 and scipy to 0.8
----------------------------------------------------------------------------------+
Reporter: maldun
| Owner: maldun
Type: task
| Status: needs_work
Priority: major
| Milestone: sage-4.6
Component: packages
| Keywords: numpy, scipy
Author: Stefan Reiterer, Francois Bissey, John Palmieri, David Kirkby
| Upstream: Fixed upstream, but not in a stable release.
Reviewer: Karl-Dieter Crisman, David Kirkby, Leif Leonhardy, Francois
Bissey | Merged:
Work_issues:
|
----------------------------------------------------------------------------------+
Comment(by kcrisman):
Replying to [comment:254 drkirkby]:
> There's a potentially helpful comment on the !SciPy list from Ralf
Gommers. It concerns ''boost'' again. It suggests we are trying to build
ppc on a system which does not support PPC. In which case, removing that
option for ppc is a necessarily and not a hack.
>
> I'm puzzled how this option gets added now though - where does it come
from?
That's what I'm trying to figure out. Usually it gets added in the spkg-
install, but apparently that's not the case here - it's coming from Scipy
itself, [http://projects.scipy.org/numpy/ticket/1399 here] (first noted by
John).
> ''You are using the 10.6 SDK and gcc 4.2. In the 10.6 SDK the ppc64
> architecture is not supported anymore, you want to use 10.4 or 10.5 SDK.
> Since Python is built with gcc 4.0 you want to do the same if you want
C++
> support for ppc64 (which you'll need for scipy.sparsetools).''
Well, not exactly. However, we always tell people that Mac Sage versions
shouldn't be expected to work on older versions of Mac than they are
created on. So what's going on here is that we'll have to likely add
something to the skpg-install or to the numpy distutils (whatever that is)
that removes the ppc64 option (perhaps both ppc options?) from the `-arch`
flags in order to get around this ''only'' in the case that we in fact
have OS X 10.6
{{{
sage: os.uname()
('Darwin', 'new-host-2.home', '10.4.0', 'Darwin Kernel Version 10.4.0: Fri
Apr 23 18:28:53 PDT 2010; root:xnu-1504.7.4~1/RELEASE_I386', 'i386')
}}}
where in particular `os.uname()[2][:2]==10` might be the thing to look at
(this is OS X 10.6, confusingly) for checking for this, otherwise allowing
a multiple architecture build.
> ''The above may be irrelevant for you though, since Sage is distributing
> binaries for each OS X version separately, right? 10.6 doesn't install
on
> ppc64 machines, so no need to build that arch at all.''
Yeah, but apparently we have to ask Scipy specifically not to build on it,
or perhaps ask Numpy not to - otherwise it's already asked for by
Numpy/Scipy, which seems confusing.
Incidentally, this exact boost thread is one of the ones I pointed out
earlier, I think ;)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9808#comment:255>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
