Hi Joel, > On the bison mailing lists, it was recently suggested that bison should > include gettext in bootstrap-tools in cfg.mk. That sounds reasonable to > me, but I see that coreutils and m4 don't do this.
The gnulib 'gettext' module is a substitute for part of what 'gettextize' or 'autopoint' installs. Since I see [1] that bison omits Makefile.in.in from the git repository, if you use the 'gettext' module, you should also ensure that you copy the files from gnulib/build-aux/po/* into po/ and runtime-po/, using "gnulib-tool --copy-file". You will then also have to invoke 'autoreconf' with AUTOPOINT=':', so that autopoint is not run. It is simpler to rely on what the 'bootstrap' script does by default. Like coreutils and m4 do. > Is there any general > rule of thumb about which tools are significant enough to be listed? When you choose from the list of gnulib modules [2], I don't understand what you mean by "significant"? Either you need a certain module, based on its description, or not. Can you rephrase the question? Bruno [1] http://git.savannah.gnu.org/gitweb/?p=bison.git;a=tree [2] http://www.gnu.org/software/gnulib/MODULES.html
