GNOME Bugzilla – Bug 341344
gconf-editor's autogen.sh does not run intltoolize
Last modified: 2006-07-11 11:18:49 UTC
using jhbuild on a Fedora Core 5 and building Gnome 2.14, the following error is produced checking for intltool >= 0.34.90... awk: cmd. line:1: fatal: cannot open file `./intltool-update.in' for reading (No such file or directory) awk: cmd. line:1: fatal: cannot open file `./intltool-update.in' for reading (No such file or directory) found ./configure: line 2028: test: : integer expression expected configure: error: Your intltool is too old. You need intltool 0.34.90 or later I'm not sure if there is any intltool 0.34.90. FC5's most recent update puts intltool at 0.34.2
upon further investigation, between versions 2.14.1 and 2.15 (based on change log), there were some changes to "configure.in" file. Specifically the addition of IT_PROG_INTLTOOL([0.34.90]) So I changed that line to #IT_PROG_INTLTOOL([0.34.90]) AC_PROG_INTLTOOL to use the macro which used to be there! Now I have a successful build. I don't know yet if everything works (I18N) or language support but at least it got compiled. One thing I noticed was that the m4 macro IT_PROG_INTLTOOL tries to access a file (among few others) which are not created at the time that it gets executed but with AC_PROG_INTLTOOL, after the compile is done, they are there. ./intltool-extract.in ./intltool-update.in ./intltool-merge.in ./intltool-update ./intltool-merge ./intltool-extract BTW, by visual comparison with gconf/configure.in, the macro IT_PROG_INTLTOOL it seems that this macro is further down in the configure.in. can this defect be caused by using IT_PROG_INTLTOOL out place?
Looks to me like gconf-editor should use gnome-autogen.sh. It will help since it will run intltoolize when necessary.
Did you use jhbuild with the -a switch? This looks like the kind of error you'd get when you don't rerun autogen after the relevant updates to configure.in.
(In reply to comment #3) > Did you use jhbuild with the -a switch? This looks like the kind of error > you'd get when you don't rerun autogen after the relevant updates to > configure.in. FWIW, I always run it with the -a switch. The problem is that the intltool-* files are absent in the source. Try a fresh chekout and you'll experience the same trouble. Simply adding them fixes it.
Elijah: The problem is with gconf-editor's autogen.sh script. It is a custom job, so isn't gnome-common's fault. The configure.in file contains: IT_PROG_INTLTOOL([0.34.90]) The autogen.sh script contains: if grep "^AC_PROG_INTLTOOL" configure.in >/dev/null; then echo "Running intltoolize..." intltoolize --copy --force --automake || exit $? fi So it never runs intltoolize. Two solutions here: 1. fix the autogen.sh script to run intltoolize if the configure.in script contains IT_PROG_INTLTOOL. 2. make the autogen.sh script call gnome-autogen.sh, removing the need to maintain yet another autogen.sh script.
Created attachment 68361 [details] [review] use gnome-autogen.sh
Commiting this since it's a build breaker.