[Numpy-discussion] Snow Leopard Py-2.7a3 _init_posix issue; IO test segfault
bsouthey at gmail.com
Mon Mar 1 20:01:04 EST 2010
On Mon, Mar 1, 2010 at 2:04 PM, Tom Loredo <loredo at astro.cornell.edu> wrote:
> Bruce Southey wrote:
> On Fri, Feb 26, 2010 at 6:59 PM, David Warde-Farley <dwf at cs.toronto.edu> wrote:
>> On 26-Feb-10, at 7:43 PM, Charles سمير Doutriaux wrote:
>>> Any idea on how to build a pure 32bit numpy on snow leopard?
>> If I'm not mistaken you'll probably want to build against the
>> Python.org Python rather than the wacky version that comes installed
>> on the system. The Python.org installer is a 32-bit Python that
>> installs itself in /Library.
>> NumPy-Discussion mailing list
>> NumPy-Discussion at scipy.org
> If you remain with 2.7 then you should also view the thread started 3 days ago:
> 'distutils problem with NumPy-1.4 & Py-2.7a3 (Snow Leopard)'
> In particular:
> Ticket 1355 - that should be resolved with r8260 (thanks Stefan):
> Ticket 1409
> Ticket 1345:
> Ticket 1409 indicates the _init_posix issue was fixed 5 days
> ago, but as of today the unnecessary _init_posix reference
> is still in the version available on SVN (r8270):
Actually the only action was that I created the ticket Feb 24 (approx
5 days ago). It does not say it was been applied or not yet.
> numpy-r8270:145$ time python setup.py build --fcompiler=gnu95
> Running from numpy source directory.Traceback (most recent call last):
> File "setup.py", line 210, in <module>
> File "setup.py", line 187, in setup_package
> from numpy.distutils.core import setup
> File "/Volumes/Tracking/Temp-work/Sandbox-installs/numpy-r8270/numpy/distutils/__init__.py", line 7, in <module>
> import ccompiler
> File "/Volumes/Tracking/Temp-work/Sandbox-installs/numpy-r8270/numpy/distutils/ccompiler.py", line 22, in <module>
> _old_init_posix = distutils.sysconfig._init_posix
> AttributeError: 'module' object has no attribute '_init_posix'
> Per Robert's suggestion, I commented out the offending line (22)
> in ccompiler.py, and the build proceeded. I am using a 64-bit
> universal build. The resulting numpy gives a segfault on test:
> test_ip_basic (test_multiarray.TestFromBuffer) ... ok
> test_multiarray.TestIO.test_ascii ... Segmentation fault
> At this point I don't know if this is just a 64-bit issue; I'm
> trying to look into it but 32-bit building for 10.6 was
> unintentionally crippled in the 2.6.x series and 2.7a3; it
> should be fixed in the next 2.7 release and in 2.6.5.
> I can also verify that this segfault bug remains:
This ticket is for that segfault and the patch just changes the
PY_VERSION_HEX to allow Python 2.7.
More information about the NumPy-Discussion