From: Nick Clifton <nickc@cambridge.redhat.com>
To: bug-binutils@gnu.org, gdb-patches@sources.redhat.com
Cc: haible@ilog.fr
Subject: Make .gmo files for distributions.
Date: Wed, 07 Nov 2001 23:31:00 -0000 [thread overview]
Message-ID: <m3y9l131zx.fsf@north-pole.nickc.cambridge.redhat.com> (raw)
Hi Guys,
Any objections to the following patch ? It adds code to the
do-proto-toplev target to build *.gmo files from their respective
.po files as part of a distribution.
I was prompted to make this change because of an email from Bruno
Haible, the GNU gettext maintainer:
http://sources.redhat.com/ml/bug-gnu-utils/2001-11/msg00130.html
He points out that not all hosts have the gettext utilities
installed, and so they cannot be expected to build the .gmo files if
they are not present in a distribution.
Cheers
Nick
2001-11-20 Nick Clifton <nickc@cambridge.redhat.com>
* Makefile.in (do-proto-toplev): Use msgfmt to generate .gmo
files from .po files for a distribution.
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/Makefile.in,v
retrieving revision 1.41
diff -p -c -r1.41 Makefile.in
*** Makefile.in 2001/11/14 05:49:24 1.41
--- Makefile.in 2001/11/20 15:12:59
*************** do-proto-toplev: $(DEVO_SUPPORT) $(SUPPO
*** 1864,1869 ****
--- 1864,1874 ----
else true; fi
chmod -R og=u . || chmod og=u `find . -print`
#
+ # Create .gmo files from .po files.
+ for f in `find . -name '*.po' -type f -print`; do \
+ msgfmt -o `echo $$f | sed -e 's/\.po$$/.gmo/'` $$f ; \
+ done
+ #
-rm -f $(PACKAGE)-$(VER)
ln -s proto-toplev $(PACKAGE)-$(VER)
next reply other threads:[~2001-11-20 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 23:31 Nick Clifton [this message]
2001-11-08 9:36 ` Andrew Cagney
2001-11-08 9:32 ` Nick Clifton
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3y9l131zx.fsf@north-pole.nickc.cambridge.redhat.com \
--to=nickc@cambridge.redhat.com \
--cc=bug-binutils@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=haible@ilog.fr \
/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