Changes between Initial Version and Version 1 of Ticket #28346


Ignore:
Timestamp:
Feb 10, 2011, 10:47:03 AM (13 years ago)
Author:
skymoo (Adam Mercer)
Comment:

NumPy has never played nice with the universal variant and I've never had much success in getting it to work. Plus it's never been high on my priority list as I personally never use universal.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #28346 – Description

    initial v1  
    55I tried to
    66
     7{{{
    78port install py27-numpy -atlas +universal
     9}}}
    810
    911with the default build_arch setting and with build_arch set to i386. The install goes trough without any errors and I can import numpy without any problem if python is running in x86_64 mode but if I start python with the command
    1012
     13{{{
    1114arch -i386 python
     15}}}
    1216
    1317and try to import numpy I always get
    1418
     19{{{
    1520File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/core/__init__.py", line 5, in <module>
    1621    import multiarray
    1722ImportError: dlopen(/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/core/multiarray.so, 2): no suitable image found.  Did find:
    1823        /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/core/multiarray.so: mach-o, but wrong architecture
     24}}}
    1925
    2026If I run lipo on this library I get:
    2127
     28{{{
    2229Non-fat file: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/core/multiarray.so is architecture: x86_64
     30}}}
    2331
    2432which seems to tell me that this library was built as 64 bit regardless of the build_arch setting.