[MacPorts] #47832: py34-h5py @ 1.8.15 +python : Import Error : Incompatible cpu-subtype

[MacPorts]

#47832: py34-h5py @ 1.8.15 +python : Import Error : Incompatible cpu-subtype
-------------------------+------------------------
  Reporter:  emmanuel@…  |      Owner:  eborisch@…
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.3.3
Resolution:              |   Keywords:
      Port:  py-h5py     |
-------------------------+------------------------

Comment (by ryandesign@…):

 Replying to [comment:2 emmanuel@…]:
 > {{{
 > Non-fat file:
 /opt/local/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4
 /site-packages/numpy/linalg/lapack_lite.so is architecture: ppc7400
 > }}}
 >
 > It seems to be the arch of the G4 family :
 [http://en.wikipedia.org/wiki/PowerPC_G4]

 I agree, that file is built for a G4 processor. The question is why. I
 suspect something in the numpy build system is deliberately requesting
 this. That could either be an accident, in which case we can change it, or
 it could be deliberate because that file requires a G4 processor, in which
 case we can do nothing about it. I have not yet found where this is
 happening but I will do a build on my G4 and take a look.

 Replying to [comment:3 eborisch@…]:
 > I think you may be out of luck here; a quick google search calls out
 lack of G3 support on apple's gcc42:
 http://www.cocoabuilder.com/archive/xcode/268796-gcc-4-2-disables-
 powerpc-g3-support.html

 That doesn't make sense. If that were so, Emmanuel would not be able to
 run ''any'' ports on his G3 anymore, but he hasn't claimed that's the
 case. There are lots of claims in that thread you linked to that are flat-
 out wrong now, at least with the updated version of Apple gcc-4.2 that we
 have in MacPorts. For example, it claims gcc-4.2 can't be used to build
 software that works on Tiger, but as of MacPorts 2.3, the MacPorts version
 of Apple gcc-4.2 is the default compiler on Tiger, and the software it
 builds certainly runs for me.

-- 
Ticket URL: <https://trac.macports.org/ticket/47832#comment:6>
MacPorts <https://www.macports.org/>
Ports system for OS X