#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):
Doesn't work, same error. That doesn't mean it wouldn't be worth keeping,
because of the other things mentioned in this thread and the scipy/boost
lists, so I am keeping this in my current attempt at an spkg.
But I think that this means the only other possible problem is the
{{{
Are the multiple "-c" options causing issues? From the build log, it
looks like "-c" is being added explicitly somewhere.
}}}
issue. From the gcc docs:
{{{
-c
Compile or assemble the source files, but do not link. The linking stage
simply is not done. The ultimate output is in the form of an object file
for each source file.
}}}
So I guess doing that twice WOULD cause the exact error message we are
seeing. Maybe once we fix that, we would still have to fix the ppc64
issue, so (as I say above) I'll keep that in for now.
{{{
compile options:
'-I/Applications/sage_builds/numpy/sage-4.6.alpha2/local/lib/python2.6
/site-packages/numpy/core/include
-c'
}}}
And then the usual `-c` is added. So where does this one come from? In
the Numpy install I see
{{{
C compiler: gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall
-Wstrict-prototypes
compile options: '-Inumpy/core/src/private -Inumpy/core/src -Inumpy/core
-Inumpy/core/src/npymath -Inumpy/core/src/multiarray
-Inumpy/core/src/umath -Inumpy/core/include -I/Users/karl-
dietercrisman/Downloads/sage-4.6.alpha3/local/include/python2.6 -c'
}}}
so at least sometimes it's okay to have `-c` in the compile options. But
I haven't got a clue where that string is set.
Also, there were two syntax errors in my initial change - here is the
corrected one:
{{{
if [ `uname` = "Darwin" ]; then
VER=`uname -r | sed 's/\([0-9]*\)\..*/\1/'`
if [ $VER -ge 10 ]; then
cp ../patches/gnu-changes.py numpy/distutils/fcompiler/gnu.py
fi
fi
}}}
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9808#comment:270>
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.
