From: Marius Vollmer <mvo@zagadka.de>
Cc: Jan Nieuwenhuizen <janneke@gnu.org>
Subject: AM_GNU_GETTEXT weirdness
Date: Fri, 24 Sep 2004 04:40:19 +0200 [thread overview]
Message-ID: <87d60c8k4s.fsf@zagadka.ping.de> (raw)
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
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2004-09-24 2:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 2:40 Marius Vollmer [this message]
2004-09-24 7:17 ` AM_GNU_GETTEXT weirdness Jan Nieuwenhuizen
2004-09-24 23:36 ` Marius Vollmer
2004-09-25 7:13 ` Jan Nieuwenhuizen
2004-09-28 16:07 ` Bruno Haible
2004-09-28 19:03 ` Marius Vollmer
2004-09-28 19:55 ` Bruno Haible
2004-09-28 21:13 ` Marius Vollmer
2004-09-25 21:30 ` Kevin Ryde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d60c8k4s.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=janneke@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).