GNOME Bugzilla – Bug 344916
intltool.m4 bails out if no perl:xml available.
Last modified: 2007-04-16 05:52:25 UTC
Hi, In Debian bug http://bugs.debian.org/360100, Wilfried Goesgens suggested that the intltool macro shouldn't fail when libxml-parser-perl isn't available, but should disable intl instead: """/usr/share/aclocal/intltool.m4 brings the following tests: AC_PATH_PROG(INTLTOOL_PERL, perl) if test -z "$INTLTOOL_PERL"; then AC_MSG_ERROR([perl not found; required for intltool]) fi if test -z "`$INTLTOOL_PERL -v | fgrep '5.' 2> /dev/null`"; then AC_MSG_ERROR([perl 5.x required for intltool]) fi if test "x$2" != "xno-xml"; then AC_MSG_CHECKING([for XML::Parser]) if `$INTLTOOL_PERL -e "require XML::Parser" 2>/dev/null`; then AC_MSG_RESULT([ok]) else AC_MSG_ERROR([XML::Parser perl module is required for intltool]) fi fi which will fail on a flat bsd install, rather then trigger a build without intl. AC_MSG_ERROR is definetlely not right here, or if, it should just be checked if all the other libintl stuff is available (which in fact wasn't) a freebsd build with the dist-tar (containing the results of autoreconf.sh of a debian box) looks like this: checking whether NLS is requested... yes checking for GNU gettext in libc... no checking for iconv... no, consider installing GNU libiconv checking for GNU gettext in libintl... no checking whether to use NLS... no checking for perl... /usr/bin/perl checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool and aborts. as there is no intl, it should build without. """ Bye,
This has nothing to do with libintl. Intltool requires perl-xml-parser to parse xml files and merge translations back into them. Disabling this in the source if it is not needed (no xml files need to be translated/merged), is well documented in the intltool documentation. This is not a bug.
as configures purpose is not only to locate programs on the disk, but also to disable features that are not available/wanted canceling configure is a bug here. There should be at least a switch like force to turn this off. 'Disabling it in the source' requires me to patch to achieve this sort of behaviour. This is clearly not what one wants to do.