GNOME Bugzilla – Bug 119615
glib-gettext.m4 obsolete macro
Last modified: 2018-05-24 10:28:48 UTC
Running 'autoreconf -Wall' in a directory containing a configure.ac which calls AM_GLIB_GNU_GETTEXT gives the warnings: "configure.ac:42: warning: The macro `AC_OUTPUT_COMMANDS' is obsolete. You should run autoupdate. configure.ac:42: warning: The macro `_AC_OUTPUT_COMMANDS_CNT' is obsolete. You should run autoupdate." AC_OUTPUT_COMMANDS has been obsolete since autoconf 2.50 and should be replaced by AC_CONFIG_COMMANDS
Created attachment 19101 [details] [review] Patch to replace AC_OUTPUT_COMMANDS has been obsolete since autoconf 2.50 and Patch to replace AC_CONFIG_COMMANDS
Patch looks wrong to me - what the code currently is doing is a "post-processing" on the po/Makefile.in.in => po/Makefile.in step that is done with normal substitution. Using a separate tag for po/Makefile won't catch the logic "if po/Makefile.in is regenerated, run this substitution and generate po/Makefile" So, using 'po/Makefile' isn't correct. But you can't use po/Makefile.in as the tag either, since you can only have one rule for a particular tag. Not really sure how to get the right effect with AC_CONFIG_COMMANDS. gettext is still using AC_OUTPUT_COMMANDS in po.m4, despite a lot of other changes.
The real problem here is that the rule in Makefile.in.in is insufficient. Currently Makefile.in.in contains: Makefile: Makefile.in.in ../config.status POTFILES cd .. \ && $(SHELL) ./config.status $(subdir)/$@.in With current autoconf, this will only regenerate Makefile.in, never Makefile. So, instead, AM_GLIB_GNU_GETTEXT should use AC_CONFIG_COMMANDS([po/Makefile], [sed -e "/POTFILES =/r po/POTFILES" po/Makefile.in > po/Makefile]) And Makefile.in.in should use: Makefile.in: Makefile.in.in ../config.status cd .. && $(SHELL) ./config.status $(subdir)/$@ Makefile: Makefile.in ../config.status POTFILES cd .. && $(SHELL) ./config.status $(subdir)/$@
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/13.