[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AM_GNU_GETTEXT weirdness
From: |
Marius Vollmer |
Subject: |
AM_GNU_GETTEXT weirdness |
Date: |
Fri, 24 Sep 2004 04:40:19 +0200 |
User-agent: |
Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) |
Hi,
running ./autogen.sh now runs gettextize and that causes some
'useless' things to happen, like the creation of po/ and the inclusion
of po/Makefile.in in _all_ AC_CONFIG_FILES statements in configure.in.
I guess all this happens for the benefit of programs that want to
internationalize/localize themselves. Right? Do we need po/?
Worse, automake now fails with:
Makefile.am:26: AM_GNU_GETTEXT used but `po' not in SUBDIRS
Including po in SUBDIRS results in
Making all in po
make[2]: Entering directory `/home/mvo/work/guile/guile-core/po'
make[2]: *** No rule to make target `all'. Stop.
make[2]: Leaving directory `/home/mvo/work/guile/guile-core/po'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/mvo/work/guile/guile-core'
make: *** [all] Error 2
So what should we do? Include po in SUBDIRS or somehow cope without
AM_GNU_GETTEXT?
Simply wrapping gettext and friends turns out to have a much larger
effect than I thought. I fully expect that there are people out there
without gettext and Guile will not build for them. What then?
Include libintl in Guile?
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
- AM_GNU_GETTEXT weirdness,
Marius Vollmer <=
- Re: AM_GNU_GETTEXT weirdness, Jan Nieuwenhuizen, 2004/09/24
- Re: AM_GNU_GETTEXT weirdness, Marius Vollmer, 2004/09/24
- Re: AM_GNU_GETTEXT weirdness, Jan Nieuwenhuizen, 2004/09/25
- Re: AM_GNU_GETTEXT weirdness, Bruno Haible, 2004/09/28
- Re: AM_GNU_GETTEXT weirdness, Marius Vollmer, 2004/09/28
- Re: AM_GNU_GETTEXT weirdness, Bruno Haible, 2004/09/28
- Re: AM_GNU_GETTEXT weirdness, Marius Vollmer, 2004/09/28
Re: AM_GNU_GETTEXT weirdness, Kevin Ryde, 2004/09/25