some autoconf issues in actual CVS

[Christian Krause]

On 29 Nov 2002 19:17:02 -0500, Derek Atkins wrote:

> This is a getttextize bug...  I'm using gettextize 0.11.1 and it
> doesn't exhibit this behavior...

Have you tried it on a clean checkout? Multiple invocations of
gettextize doesn't modify the configure.in. I've tried it with 0.11.1
and there I get the error too.

I read a little bit in the info manual of gettext and found some
interesting facts:

" It is also important to understand that `gettextize' is not part of
the GNU build system, in the sense that it should not be invoked
automatically, and not be invoked by someone who doesn't assume the
responsibilities of a package maintainer. "

In the info manual of gettext is a section about using gettext with CVS
where the whole problem is discussed (autopoint may help... ).

btw, automatic calling is not possible in newer versions of gettext
(0.11.5), they want an interactive _terminal_ input...

regards,
christian

>> configure.in:1141: error: `intl/Makefile' is already registered with AC_CONFIG_FILES.
>> autoconf/status.m4:844: AC_CONFIG_FILES is expanded from...
>> configure.in:1141: the top level
>> autom4te: /usr/bin/m4 failed with exit status: 1
>> autoheader: /usr/bin/autom4te failed with exit status: 1
>> **Error**: autoheader failed.
>> 
>> This error is caused by duplicate entries in AC_OUTPUT in
>> configure.in. These duplicate entries are generated by gettextize called
>> in autogen.sh.
>> 
>> In the CVS the configure.in is correct:
>> -------------------------------------
>> AC_OUTPUT( m4/Makefile  intl/Makefile
>> -------------------------------------
>> 
>> After running autogen.sh, the configure.in is changed. This is done by
>> the gettexttize call: gettextize --force --copy --intl
>> 
>> -------------------------------------------------------------------
>> AC_OUTPUT( m4/Makefile  intl/Makefile  intl/Makefile po/Makefile.in
>> -------------------------------------------------------------------
>> (the po/Makefile.in entry is duplicated too; its listed some lines
>> below)
>> 
>> 
>> I don't know whether it's a bug of gnucash or gettextize (version
>> 0.11.5).