[MacPorts] #35533: p5.12-xml-parser: Couldn't find your C compiler
MacPorts
noreply at macports.org
Sun Sep 2 11:25:49 PDT 2012
#35533: p5.12-xml-parser: Couldn't find your C compiler
-----------------------------------+----------------------------------------
Reporter: Onemer117@… | Owner: mjg@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.1.2
Keywords: haspatch | Port: p5.12-xml-parser
-----------------------------------+----------------------------------------
Comment(by devans@…):
I ran into this same problem today while doing a clean install of MacPorts
on a Snow Leopard test machine.
My configuration:
{{{
Mac OSX 10.6.8, x86_64, XCode 3.2.6, MacPorts 2.1.2
}}}
As reported above, I agree that this port (and possibly other Perl ports)
are using Config.pm alone to determine the correct compiler path to use.
The trouble occurs when this does not match the current Xcode compiler
path (which MacPorts correctly identifies).
If my case, Config.pm says
{{{
'/usr/bin/gcc-4.2' (doesn't exist here)
}}}
but MacPorts says
{{{
'/Developer/usr/bin/gcc-4.2' (which is correct)
}}}
perl5 (perl5.12 @5.12.4_1+universal) was installed from binary archive.
Rebuilding perl5 from source on this machine
{{{
sudo port -f uninstall perl5.12 @5.12.4_1+universal
sudo port -s install perl5.12 @5.12.4_1+universal
}}}
solved the problem without any further patches.
So I conclude that the build environment for the binary archive and mine
are different, possibly an Xcode installation problem.
I'm thinking there is a missing symbolic link from /usr/bin/gcc-4.2 ->
/Developer/usr/bin/gcc-4.2 here?
--
Ticket URL: <https://trac.macports.org/ticket/35533#comment:9>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list