Re: Bug in gettextize or related components

[Bruno Haible]

> dnl Languages which your application supports
> ALL_LINGUAS=""
> AM_GNU_GETTEXT
> AM_GNU_GETTEXT_VERSION(0.10.40)

This is ok; 'autopoint' thus copies the gettext-0.10.40 Makefile.in.in and
macros into your package.

> $ aclocal --print-ac-dir
> /usr/share/aclocal
>
> ... tons of files in this dir, contributed by many packages.  Using m4
> directory in the invocation:
>
> $ aclocal --acdir=`pwd`/m4
> aclocal: configure.in: 7: macro `AM_INIT_AUTOMAKE' not found in library
> aclocal: configure.in: 8: macro `AM_CONFIG_HEADER' not found in library
> aclocal: configure.in: 13: macro `AM_PROG_CC_STDC' not found in library
> aclocal: configure.in: 15: macro `AM_PROG_LIBTOOL' not found in library
>
> On the other hand,
>
> $ aclocal
>
> runs without comment, but neither copies or generates po/Makefile.in.in.

What you need is
  $ aclocal -I m4
It looks in both the m4/ and the /usr/share/aclocal/ directory, giving
priority to the m4/ directory.

It's such a 'aclocal' invocation without arguments which can put the wrong
autoconf macros into aclocal.m4 and thus into 'configure'.

> The anjuta build log has the following:
>
> Generating Project ...
> Loading Project ...
> Saving Project ...
> Generating source codes ...
> Copying icon file ...
> Locating files ...
> Saving Project ...
> Updating Project ...
> Running autogen.sh ...
> **Warning**: I am going to run `configure' with no arguments.
> If you wish to pass any to it, please specify them on the
> ./autogen.sh' command line.
>
> processing .
> Creating ./aclocal.m4 ...
> Running gettextize...  Ignore non-fatal messages.
>   autopoint --force

1) It would be interesting to know with which options anjuta creates
the aclocal.m4.

2) There is definitely a bug in anjuta here: it should invoke autopoint
_before_ creating the aclocal.m4, not afterwards. The reason being
precisely that when 'aclocal' is run, to create aclocal.m4, it must see
the *.m4 files that 'autopoint' brings in.

Bruno