[MacPorts] #22360: py26-numpy won't build

[MacPorts]

#22360: py26-numpy won't build
--------------------------+-------------------------------------------------
 Reporter:  ak@…          |       Owner:  mcalhoun@…           
     Type:  defect        |      Status:  new                  
 Priority:  Normal        |   Milestone:                       
Component:  ports         |     Version:  1.8.1                
 Keywords:                |        Port:  py26-numpy           
--------------------------+-------------------------------------------------

Comment(by anishmuttreja@…):

 ==  ==
 From the debug log attached to the bug, it seems gcc-mp-4.3 may have
 failed because of this

 804     don't know how to compile Fortran code on platform 'posix'
 805     C compiler: /opt/local/bin/gcc-mp-4.3 -arch x86_64 -arch i386
 -isysroot / -fno-strict-aliasing -fno-common -dynamic -DNDEBUG -g -fwrapv
 -O3 -Wall -Wstrict-prototypes
 806
 807     compile options: '-Inumpy/core/src -Inumpy/core/include
 -I/opt/local/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6
 -c'
 808     gcc-mp-4.3: _configtest.c
 806
 807     compile options: '-Inumpy/core/src -Inumpy/core/include
 -I/opt/local/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6
 -c'
 808     gcc-mp-4.3: _configtest.c
 809     cc1: error

 Might this be why builds with python26+universal fail and builds with
 python26 -universal work.
 From the gcc manual

 > man gcc-mp-4.3
 "FSF GCC on Darwin does not create "fat" object files; it will create an
        object file for the single architecture that it was built to
 target.
        Apple's GCC on Darwin does create "fat" files if multiple -arch
 options
        are used; it does so by running the compiler or linker multiple
 times
        and joining the results together with lipo."

 Can the gcc maintainer take a look?

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