[MacPorts] #17884: gimp2 2.6.4 build fails
David Evans
devans at macports.org
Mon Jan 5 09:37:42 PST 2009
MacPorts wrote:
> #17884: gimp2 2.6.4 build fails
> -------------------------------------+--------------------------------------
> Reporter: calle.kabo@… | Owner: macports-tickets@…
> Type: defect | Status: new
> Priority: Normal | Milestone: Port Bugs
> Component: ports | Version: 1.7.0
> Keywords: gimp2 2.6.4 XML::Parser | Port: gimp2
> -------------------------------------+--------------------------------------
> I got an error when upgrading to gimp2 2.6.4.
> {{{
> checking for XML::Parser... configure: error: XML::Parser perl module is
> required for intltool
> }}}
>
Replying by email as trac doesn't seem to be working this morning.
I tried rebuilding gimp2 this morning but was unable to reproduce this
problem.
> So I did:
> {{{
> $ sudo cpan
> cpan> install XML::Parser
> }}}
>
This is unnecessary (and perhaps not desireable) as XML::Parser is
provided by port
p5-xml-parser which is declared as a dependency by the gimp2 port.
If fact, the output you submitted says that this port is installed:
DEBUG: Found port in
file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/perl/p5
-xml-parser
DEBUG: epoch: in tree: 0 installed: 0
DEBUG: p5-xml-parser 2.36_0 exists in the ports tree
DEBUG: p5-xml-parser 2.36_0 is installed
DEBUG: No need to upgrade! p5-xml-parser 2.36_0 >= p5-xml-parser 2.36_0
So there is potentially some problem with your perl configuration or the
installation of p5-xml-parser
Try the following command (this is the test configure uses)
$ /opt/local/bin/perl -e "require XML::Parser"
This should complete silently without any error but is apparently not
doing so in configure's
context at least. Any error output from this may point you in the
proper direction.
Of course
$ which perl
should return
/opt/local/bin/perl
Again, from your output, configure seems to have properly detected this.
If nothing else works you might try
$ sudo port -fn upgrade p5-xml-parser
to force p5-xml-parser to reinstall in case its installation is damaged
in some way.
I thought originally that this might be a result of the recent upgrade
of perl from 5.8.8 to
5.8.9 (which it looks like you have completed) but that doesn't seem to
be an issue on
my system (10.4.11 ppc) at least.
Sorry I can't be of more help right now but please reply with any
further information you
may develop.
More information about the macports-dev
mailing list