#9808: Upgrade numpy to 1.4.1 and scipy to 0.8
-----------------------------------+----------------------------------------
Reporter: maldun | Owner: maldun
Type: task | Status: needs_review
Priority: major | Milestone: sage-4.6
Component: packages | Keywords: numpy, scipy
Author: Stefan Reiterer | Upstream: N/A
Reviewer: Karl-Dieter Crisman | Merged:
Work_issues: |
-----------------------------------+----------------------------------------
Comment(by kcrisman):
Replying to [comment:69 maldun]:
> Replying to [comment:68 kcrisman]:
> > Sadly, same error. This is probably on my end, but this is a
supported architecture so it's important to know what went wrong. I don't
think that the `./sage -ba` would have anything to do with it.
> >
> > So I suspect that the "missing: `Python.h` is the problem, as I've
seen a few other things about this online (including ones like this one,
where /include/Python.h definitely exists, here it's within the
`$SAGE_ROOT` directory). I wonder why it's not finding it this time?
>
> Question: Have you tried to give the direct path to the compiler?
No - how would I do that?
> And does in OS X gcc points to /include/Python.h because in sage it's
/include/python2.6/Python.h ?
I find that very unlikely, since everything else works fine and in general
Sage builds fine on OS X 10.4-10.6. But sometimes things get mixed up,
I'm sure. There aren't any weird env variables that would do that here,
though, I don't think.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9808#comment:70>
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.
