Incorrect usage of intltool configuration macros
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Won't Fix
|
High
|
Alex Valavanis | ||
0.92.x |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
The Debian maintainer, Matteo Vescovi, has reported an issue in 0.91 to me by email, which is exposed when using autoreconf instead of ./autogen.sh:
<quote>
The autoreconf commit changes the way configure.ac is processed and it
fails badly, as you can see at [1], where the error is:
config.
Obviously, that file exists already.
Comparing upstream configure.ac from 0.48.5 and 0.91 releases, I grabbed
the relevant part following:
@@ -148,12 +211,14 @@ fi
dnl *******
dnl Gettext stuff
dnl *******
+IT_PROG_
+
+AM_GNU_
+AM_GNU_
+
This is a problem. Intltool and Gettext clashed if used at the same time.
And autoreconf finally brought this issue out.
It has already been discovered[2] and explained[3].
<snip />
[1] http://
[2] https:/
[3] https:/
</quote>
tags: | added: bug-migration |
This is related to our earlier issue in bug #992047 (comment #35 onwards), which was "fixed" by a fairly horrible hack in autogen.sh: https:/ /launchpadlibra rian.net/ 132587610/ fix-locale- path-v2. patch
It seems that the current advice is to only use the IT_PROG_INTLTOOL macro, and not the AM_GNU_GETTEXT* macros:
https:/ /code.launchpad .net/~robert- ancell/ intltool/ remove- am-gnu- gettext/ +merge/ 114274