From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: AM_GNU_GETTEXT weirdness
Date: Sun, 26 Sep 2004 07:30:01 +1000 [thread overview]
Message-ID: <878yayhw9y.fsf@zip.com.au> (raw)
In-Reply-To: <87d60c8k4s.fsf@zagadka.ping.de> (Marius Vollmer's message of "Fri, 24 Sep 2004 04:40:19 +0200")
Marius Vollmer <mvo@zagadka.de> writes:
>
> inclusion
> of po/Makefile.in in _all_ AC_CONFIG_FILES statements in configure.in.
That's probably a bug :).
> Do we need po/?
I suppose only if guile's own messages are to be localized.
> make[2]: Entering directory `/home/mvo/work/guile/guile-core/po'
> make[2]: *** No rule to make target `all'. Stop.
Try re-running configure (I think ... maybe).
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-09-25 21:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 2:40 AM_GNU_GETTEXT weirdness Marius Vollmer
2004-09-24 7:17 ` 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 [this message]
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=878yayhw9y.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@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).