[MacPorts] #27002: py26-numpy @1.5.0, Revision 1 - build failure
MacPorts
noreply at macports.org
Mon Nov 29 05:49:24 PST 2010
#27002: py26-numpy @1.5.0, Revision 1 - build failure
---------------------------------+------------------------------------------
Reporter: dannowolk@… | Owner: mcalhoun@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.1
Keywords: tiger | Port: py26-numpy
---------------------------------+------------------------------------------
Comment(by stephen@…):
This bug is still present in py26-numpy @1.5.1_0 (and py25-numpy
@1.5.1_0).
I suspect that the problem is that something is forcing the use of
/usr/bin/gcc-4.0
for the build, regardless of the setting of configure.cc (and
configure.compiler,
for that matter). I thought it was Python itself -- I know that Python
does care
about the core compiler when building C extensions -- but maybe it isn't.
Anyway,
the compiler controller is visible in the trace above.
I tried rebuilding the python26 port with "configure.compiler macports-
gcc-4.4"
hacked into the Portfile. It seemed to succeed (at least the compiler
used to
compile much of Python and its extensions was gcc-mp-4.4) However, in
building
py26-numpy, once again /usr/bin/gcc-4.0 was forced as the compiler, and
later on
the build totally blew up with "cannot link a simple C program" (because
the
Macports gcc doesn't recognize the -arch command-line option, it seems).
The only other thing I can think of to try is to install the apple-gcc-4.2
port,
and rebuild python26 and all my py26-* ports with that compiler. But on a
slow
iBook G4 installing a new gcc will take forever, and rebuilding everything
that
depends on python26 as well as python itself will take almost that long;
I'm
not eager to do this.
--
Ticket URL: <https://trac.macports.org/ticket/27002#comment:11>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list