Opened 18 years ago

Closed 18 years ago

Last modified 18 years ago

#8731 closed defect (invalid)

gimp2 will not build - configure error "XML::Parser perl module is required for intltool"

Reported by: ghenshaw@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.2
Keywords: Cc: andrewmy@…
Port:

Description

sudo port clean --all gimp2 sudo port upgrade gimp2

---> Configuring gimp2 Error: Target com.apple.configure returned: configure failure: shell command "cd "/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_graphics_gimp2/work/gimp-2.2.11" && LDFLAGS=-L/opt/local/lib CPPFLAGS=-I/opt/local/include ./configure --prefix=/opt/local --enable-mp --mandir=/opt/local/share/man" returned error 1 Command output: checking for _LARGE_FILES value needed for large files... no checking whether to turn on debugging... no checking whether to turn on profiling... no checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking for ANSI C header files... (cached) yes checking for sys/wait.h that is POSIX.1 compatible... yes checking whether time.h and sys/time.h may both be included... yes checking sys/param.h usability... yes checking sys/param.h presence... yes checking for sys/param.h... yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking sys/times.h usability... yes checking sys/times.h presence... yes checking for sys/times.h... yes checking for sys/wait.h... (cached) yes checking for unistd.h... (cached) yes checking for pid_t... yes checking return type of signal handlers... void checking for vprintf... yes checking for _doprnt... no checking for working alloca.h... yes checking for alloca... yes checking for difftime... yes checking for putenv... yes checking for mmap... yes checking for perl... /opt/local/bin/perl checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool

Change History (7)

comment:1 Changed 18 years ago by andrewmy@…

Cc: andrewmy@… added

I had this problem, and I found that uninstalling p5-xml-parser and then trying to upgrade gimp2 resolved it. Not sure why, but it's at least a quick fix.

port -f uninstall p5-xml-parser port upgrade gimp2

comment:2 Changed 18 years ago by ghenshaw@…

I just tried that, and it didn't work for me - it reinstalled p5-xml-parser and then halted with the same configuration error trying to upgrade gimp2.

comment:3 Changed 18 years ago by danielluke (Daniel J. Luke)

You probably have p5-xml-parser built against an older perl install.

You need to do:

port -f uninstall p5-xml-parser port clean --all p5-xml-parser port install p5-xml-parser

comment:4 Changed 18 years ago by ghenshaw@…

That works, although it was painful - several errors along the way, including complaints about not being able to deactivate gimp2 2.2.10-0 and about /opt/local/share/applications not existing. Weird.

(In reply to comment #3)

You probably have p5-xml-parser built against an older perl install.

You need to do:

port -f uninstall p5-xml-parser port clean --all p5-xml-parser port install p5-xml-parser

comment:5 Changed 18 years ago by danielluke (Daniel J. Luke)

Resolution: invalid
Status: newclosed

comment:6 Changed 18 years ago by ghenshaw@…

Err... before this bug is closed, how is it invalid? Shouldn't the port system have been able to handle the dependency on a current build p5-xml-parser automatically, without manual intervention?

comment:7 Changed 18 years ago by danielluke (Daniel J. Luke)

(In reply to comment #5)

Err... before this bug is closed, how is it invalid? Shouldn't the port system have been able to handle the dependency on a current build p5-xml-parser automatically, without manual intervention?

It's invalid because it's not a gimp bug, and it's not a problem with darwinports detecting p5-xml-parser (since it was installed, just broken).

The issue is that when you upgrade perl, you need to rebuild some of the perl modules (some will work after an upgrade/some won't).

There's already support for rebuilding all of a port's dependents in cvs HEAD and I think there's a bug open for this issues as well (it might be nice for ports to be able to indicate that they need to be rebuilt if one of their dependencies is upgraded).

Note: See TracTickets for help on using tickets.