GNOME Bugzilla – Bug 706846
build fails due to side-by-side IT_PROG_INTLTOOL and AM_GNU_GETTEXT
Last modified: 2013-08-28 18:01:30 UTC
Created attachment 253197 [details] [review] Patch to fix build Per https://bugzilla.gnome.org/show_bug.cgi?id=705365, using both IT_PROG_INTLTOOL and AM_GNU_GETTEXT is unsupported. Changes in gnome-common master cause build to break with this combination.
Review of attachment 253197 [details] [review]: Thanks for the patch. Looks good. Do you have push rights?
Review of attachment 253197 [details] [review]: Yes. Changes pushed. https://git.gnome.org/browse/gtksourceview/commit/?id=da370b1bb989e0a50f11e062be635bcd846c72fa
Now I get the following warning messages: > gtksourceview-i18n.c: In function '_gtksourceview_gettext': > gtksourceview-i18n.c:81:3: warning: statement with no effect [-Wunused-value] > gtksourceview-i18n.c:84:3: warning: statement with no effect [-Wunused-value] Before your patch, these warnings appeared only when using the --disable-nls configure option. Now it seems that ENABLE_NLS is always false (or more precisely, not defined). For the commit message, just a little nitpick, you forgot to add an empty line after the title (see the HACKING file for the instructions on commit messages).
fyi, I think we tried this before and we ended up reverting the patches since the software was not translated anymore...
It appears that bindtextdomain wants to see ENABLE_NLS defined or it won't do anything. I'm a little confused, as gnome-shell (which I patched similarly) appears to be localized correctly, but on testing that doesn't appear to be the case for gtksourceview. I'm looking into alternatives.
Created attachment 253411 [details] [review] define ENABLE_NLS if NLS is used The attached patch solves the warnings by using AC_DEFINE to define ENABLE_NLS if NLS is used. It fixes the warnings for me.
David's patch appears to be the correct behavior. IT_PROG_INTLTOOL should define ENABLE_NLS upstream, and I've filed a bug against upstream to that effect: https://bugs.launchpad.net/intltool/+bug/1217976. In the meantime, I believe the patch should resolve the issue.
Review of attachment 253411 [details] [review]: Thanks, I've tested, and the translations work again. And the --disable-nls option works too.