[MacPorts] #35533: p5.12-xml-parser: Couldn't find your C compiler
MacPorts
noreply at macports.org
Wed Sep 5 01:25:29 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 piet@…):
Replying to [comment:9 devans@…]:
> 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)
> }}}
I have XCode 4.2 but there is no /Developer/usr/bin/gcc-4.2.
>
> 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.
I also did this and now the Config.pm has /usr/bin/clang as C compiler.
With this setting now uninstalling p5-xml-parser and reinstalling it from
source succeeds without problems. Why my previous upgrade of perl5 did not
solve it I don't know. Maybe just an upgrade isn't thorough enough.
--
Ticket URL: <https://trac.macports.org/ticket/35533#comment:11>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list