[MacPorts] #28346: cannot build py27-numpy as i386 on SnowLeopard

[MacPorts]

#28346: cannot build py27-numpy as i386 on SnowLeopard
----------------------------------------+-----------------------------------
 Reporter:  dumont.guillaume@…          |       Owner:  macports-tickets@…                   
     Type:  defect                      |      Status:  new                                  
 Priority:  Normal                      |   Milestone:                                       
Component:  ports                       |     Version:  1.9.2                                
 Keywords:                              |        Port:  py27-numpy                           
----------------------------------------+-----------------------------------
 Hi,

 I am trying to build numpy with python 2.7 as a 32 bit since I would like
 to use the wxpython port and the numpy port with the same version of
 python.

 I tried to

 port install py27-numpy -atlas +universal

 with 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

 arch -i386 python

 and try to import numpy I always get

 File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/numpy/core/__init__.py", line 5, in <module>
     import multiarray
 ImportError:
 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:
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/numpy/core/multiarray.so: mach-o, but wrong architecture

 If I run lipo on this library I get:

 Non-fat file:
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/numpy/core/multiarray.so is architecture: x86_64

 which seems to tell me that this library was built as 64 bit regardless of
 the build_arch setting.

 Is this a known problem?

 Thanks

-- 
Ticket URL: <https://trac.macports.org/ticket/28346>
MacPorts <http://www.macports.org/>
Ports system for Mac OS