Created attachment 289619 [details] build log On my hardened ~amd64 machine with gcc 4.6.1 I see the following failure in the numpy-testsuite. I'm not convinced that this is a failure, but it looks more like a bug in the testsuite itself. Here we go: ====================================================================== ERROR: Failure: OSError (/var/tmp/portage/dev-python/numpy-1.5.1/work/numpy-1.5.1/test-3.2/lib/python/numpy/core/multiarray.p yd: cannot open shared object file: No such file or directory) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib64/python3.2/site-packages/nose/failure.py", line 37, in runTest raise self.exc_class(self.exc_val).with_traceback(self.tb) File "/usr/lib64/python3.2/site-packages/nose/loader.py", line 390, in loadTestsFromName addr.filename, addr.module) File "/usr/lib64/python3.2/site-packages/nose/importer.py", line 39, in importFromPath return self.importFromDir(dir_path, fqname) File "/usr/lib64/python3.2/site-packages/nose/importer.py", line 86, in importFromDir mod = load_module(part_fqname, fh, filename, desc) File "/var/tmp/portage/dev-python/numpy-1.5.1/work/numpy-1.5.1/test-3.2/lib/python/numpy/tests/test_ctypeslib.py", line 8, in <module> cdll = load_library('multiarray', np.core.multiarray.__file__) File "/var/tmp/portage/dev-python/numpy-1.5.1/work/numpy-1.5.1/test-3.2/lib/python/numpy/ctypeslib.py", line 122, in load_library raise exc File "/var/tmp/portage/dev-python/numpy-1.5.1/work/numpy-1.5.1/test-3.2/lib/python/numpy/ctypeslib.py", line 119, in load_library return ctypes.cdll[libpath] File "/usr/lib64/python3.2/ctypes/__init__.py", line 415, in __getitem__ return getattr(self, name) File "/usr/lib64/python3.2/ctypes/__init__.py", line 410, in __getattr__ dll = self._dlltype(name) File "/usr/lib64/python3.2/ctypes/__init__.py", line 340, in __init__ self._handle = _dlopen(self._name, mode) OSError: /var/tmp/portage/dev-python/numpy-1.5.1/work/numpy-1.5.1/test-3.2/lib/python/numpy/core/multiarray.pyd: cannot open shared object file: No such file or directory ---------------------------------------------------------------------- Ran 3000 tests in 123.416s FAILED (KNOWNFAIL=5, SKIP=5, errors=1)
Created attachment 289621 [details] emerge --info
*** This bug has been marked as a duplicate of bug 351057 ***
The bug to which this one was resolved is marked as fixed, but I still see this behavior. So I reopened.
(In reply to comment #3) Do you use dev-python/numpy-1.6.1-r1?
No, I still use numpy-1.5.1 since sage needs it and no higher version.
sorry about sage still using 1.5.1. It is becoming a pain in the ass. But I now think the thing preventing the upgrade may be a bug in numpy-1.6.x. See http://trac.sagemath.org/sage_trac/ticket/11334 for details.
Another data point: numpy-1.6.1-r1 merges fine. A pity, that sage doesn't like it.
+ 07 Dec 2012; Justin Lecher <jlec@gentoo.org> -numpy-1.5.1.ebuild, + -numpy-1.6.0.ebuild, -numpy-1.6.1.ebuild: + Drop old, fixes #404435, #386847 +
