[MacPorts] #22936: numpy atlas segmentation fault

[MacPorts]

#22936: numpy atlas segmentation fault
-------------------------------+--------------------------------------------
 Reporter:  jjstickel@…        |       Owner:  mcalhoun@…                 
     Type:  defect             |      Status:  new                        
 Priority:  Normal             |   Milestone:                             
Component:  ports              |     Version:  1.8.1                      
 Keywords:                     |        Port:  py25-numpy py26-numpy atlas
-------------------------------+--------------------------------------------

Comment(by jameskyle@…):

 I worked a bit with mark above and he provided some good feedback. The
 problem seems pretty elusive, but I did notice one discrepancy between my
 install on 10.6 and his install on tiger.

 py26-numpy (and atlas) are built using gcc43 by default.

 On my system, besides the core atlas libraries, the py26-numpy libs are
 only linked to the libSystem.B.dylib library.

 {{{
 /opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/numpy/core/_dotblas.so:
         /opt/local/lib/libptf77blas.dylib (compatibility version 0.0.0,
 current version 0.0.0)
         /opt/local/lib/libptcblas.dylib (compatibility version 0.0.0,
 current version 0.0.0)
         /opt/local/lib/libatlas.dylib (compatibility version 0.0.0,
 current version 0.0.0)
         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
 version 124.1.1)
 }}}

 The cblas libraries on 10.4, however, were also linked against the system
 gcc libraries:

 {{{
 /opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6
 /site-packages/numpy/core/_dotblas.so:
  /opt/local/lib/libptf77blas.dylib (compatibility version 0.0.0, current
 version 0.0.0)
  /opt/local/lib/libptcblas.dylib (compatibility version 0.0.0, current
 version 0.0.0)
  /opt/local/lib/libatlas.dylib (compatibility version 0.0.0, current
 version 0.0.0)
  /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version
 1.0.0) <==================
  /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
 111.1.4)
 }}}

 I could easily see cross linking leading to incorrect symbol lookups and
 the segfault behavior being seen.

 This would also be in the py26-numpy build process, if I have time this
 weekend I'll give it a closer look.

 -james

-- 
Ticket URL: <http://trac.macports.org/ticket/22936#comment:9>
MacPorts <http://www.macports.org/>
Ports system for Mac OS