Description of problem: Attemping to rebuild numpy against 2.7 thus: koji build dist-f14-py27-rebuild $(make cvsurl) (from tagged CVS checkout) dies with a segfault in %check: http://koji.fedoraproject.org/koji/getfile?taskID=2337411&name=build.log I'll attach a backtrace. I did some searching and found some references to porting numpy to 2.7 http://mail.scipy.org/pipermail/numpy-discussion/2010-June/051207.html http://old.nabble.com/Numpy-1.5-for-Python-2.7-and-3.1-td28995808.html http://projects.scipy.org/numpy/ticket/1520 It's not clear to me what API/ABI approaches they're following, and is this is applicable to 1.4.1. Version-Release number of selected component (if applicable): numpy-1.4.1-4.fc14 How reproducible: 100% Steps to Reproduce: Simulate the %check from the build thus: 1. cd rpmbuild/BUILD/numpy-1.4.1/doc 2. PYTHONPATH=/root/rpmbuild/BUILDROOT/numpy-1.4.1-4.fc14.x86_64/usr/lib64/python2.7/site-packages gdb --args /usr/bin/python -c "import pkg_resources, numpy ; numpy.test()" Unfortunately symbols have been stripped at this point; I wonder what the best way to regenerate this one is
Created attachment 433816 [details] Backtrace from segfault
Seems to be this: http://www.mail-archive.com/numpy-discussion@scipy.org/msg22626.html
http://projects.scipy.org/numpy/changeset/8387/trunk/numpy/core/src/multiarray/numpyos.c
changeset 8387 is layered on top of http://projects.scipy.org/numpy/changeset/7926/trunk/numpy/core/src/multiarray/numpyos.c
I've committed a version of this to CVS as numpy-1.4.1-6.fc14 Attempting a rebuild: http://koji.fedoraproject.org/koji/taskinfo?taskID=2343683
The build succeeded. There are a lot of failures in the selftest in the %check, but that doesn't seem to stop the build: see e.g. http://koji.fedoraproject.org/koji/getfile?taskID=2343685&name=build.log > Ran 2395 tests in 10.666s > FAILED (KNOWNFAIL=4, errors=9, failures=3) and a lot of noise due to deprecation. At least some of this seems to have been fixed upstream.