On Sep 15, 2019, at 23:36, Dave Horsfall wrote:
> Trying to install the GQ LDAP browser I traced the failure to the Perl module
> "XML::Parser" being required.
Often, an error message seen when running a ./configure script saying that
XML::Parser is required is erroneous, and actually means that that configure
script contains boilerplate code to detect the presence of intltool--code which
incorrectly believes that it should check for the presence of XML::Parser. It
should not. intltool uses XML::Parser internally, but that is of no concern to
any programs that will be using intltool, and specifically, the version of perl
that was used to build intltool in MacPorts may not be the version of perl that
the user has set as the default now. We have patched intltool in MacPorts not
to do that when generating its boilerplate code [1], but unfortunately, the
buggy code gets copied into every configure script generated with the broken
intltool (for example, the intltool installed on every non-MacPorts-using
developer's system), so you may have to run autoreconf (or run the project's
./autogen.sh or ./bootstrap script if it has one) to regenerate the configure
script correctly.
[1]
https://github.com/macports/macports-ports/blob/master/textproc/intltool/files/patch-remove-intltool-perl-hack.diff
Wouldn't it be great if we could get that patch incorporated into the upstream
intltool sources?
