Re: Possible po.m4 bug in gettext-0.16.1.tar.gz po.m4 -- using "--statistics" to check for msgfmt

[Bruno Haible]

Mark Moriarty wrote:
> I actually built their extras/contrib.
> That process downloads, builds, and installs gettext-0.16.1.tar.gz

Ah, indeed: The file 'bootstrap' there contains the lines
    i686-pc-cygwin)
            echo "HAVE_WIN32 = 1" >> config.mak
            CC="gcc -mno-cygwin -isystem /usr/include/mingw"
            CXX="g++ -mno-cygwin -isystem /usr/include/mingw"
            HOST=`$CC -dumpmachine`
            EXTRA_CFLAGS=" -mno-cygwin -isystem /usr/include/mingw"
            EXTRA_CPPFLAGS=" -mno-cygwin -isystem /usr/include/mingw"
            EXTRA_LDFLAGS=" -mno-cygwin"
            echo "PKG_CONFIG_PATH = \$(PREFIX)/lib/pkgconfig" >> config.mak

This is the proof that you built mingw binaries of GNU gettext, not
Cygwin binaries.

The problem is that msgfmt.exe does not understand the /dev/null
argument (since in mingw, the null file has the name "NUL", not "/dev/null").
I'm adding a workaround like this:

2007-10-06  Bruno Haible  <address@hidden>

        * autogen.sh (GNULIB_MODULES_TOOLS_FOR_SRC): Add open, fopen.
        (GNULIB_MODULES_LIBGETTEXTPO): Add fopen.
        Reported by Mark Moriarty <address@hidden>.

> Within gettext-0.16.1.tar.gz, there is gettext/gettext-runtime/m4/po.m4
> That particular file, the po.m4, is "old"  as can be seen at line 1 of it:
> # po.m4 serial 13 (gettext-0.15)
> 
> Lines 36 - 39 of the po.m4 file, the one that's provided in the tar.gz,
> consist of:
>   AM_PATH_PROG_WITH_TEST(MSGFMT, msgfmt,
>     [$ac_dir/$ac_word --statistics /dev/null >&]AS_MESSAGE_LOG_FD[ 2>&1 &&
>      (if $ac_dir/$ac_word --statistics /dev/null 2>&1 >/dev/null | grep
> usage >/dev/null; then exit 1; else exit 0; fi)],
>     :)

This po.m4 is all right, for the reasons explained in the previous mails.

Bruno