From: Petr Ovtchenkov <ptr@void-ptr.info>
To: bug-gnulib@gnu.org
Cc: Petr Ovtchenkov <ptr@void-ptr.info>
Subject: [PATCH 1/1] old-fashioned suffix rules cannot have any prerequisites
Date: Wed, 1 Apr 2020 16:12:54 +0300 [thread overview]
Message-ID: <20200401131254.1330-2-ptr@void-ptr.info> (raw)
In-Reply-To: <20200401131254.1330-1-ptr@void-ptr.info>
See:
https://www.gnu.org/software/make/manual/html_node/Suffix-Rules.html#Suffix-Rules
<snip>
Suffix rules cannot have any prerequisites of their own. If they have
any, they are treated as normal files with funny names, not as suffix
rules. Thus, the rule:
...
</snip>
---
build-aux/po/Makefile.in.in | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/build-aux/po/Makefile.in.in b/build-aux/po/Makefile.in.in
index e4169b338..320cef068 100644
--- a/build-aux/po/Makefile.in.in
+++ b/build-aux/po/Makefile.in.in
@@ -107,7 +107,7 @@ DISTFILESDEPS = $(DISTFILESDEPS_$(DIST_DEPENDS_ON_UPDATE_PO))
# the .pot file. This eliminates the need to update the .po files when the
# .pot file has changed, which would be troublesome if the .po files are put
# under version control.
-.po.gmo: $(srcdir)/$(DOMAIN).pot
+%.gmo: %.po $(srcdir)/$(DOMAIN).pot
@lang=`echo $* | sed -e 's,.*/,,'`; \
test "$(srcdir)" = . && cdcmd="" || cdcmd="cd $(srcdir) && "; \
echo "$${cdcmd}rm -f $${lang}.gmo && $(MSGMERGE) $(MSGMERGE_FOR_MSGFMT_OPTION) -o $${lang}.1po $${lang}.po $(DOMAIN).pot && $(GMSGFMT) -c --statistics --verbose -o $${lang}.gmo $${lang}.1po && rm -f $${lang}.1po"; \
@@ -118,7 +118,7 @@ DISTFILESDEPS = $(DISTFILESDEPS_$(DIST_DEPENDS_ON_UPDATE_PO))
mv t-$${lang}.gmo $${lang}.gmo && \
rm -f $${lang}.1po
-.sin.sed:
+%.sed: %.sin
sed -e '/^#/d' $< > t-$@
mv t-$@ $@
@@ -444,14 +444,14 @@ update-po: Makefile
# General rule for creating PO files.
-.nop.po-create:
+%.po-create: %.nop
@lang=`echo $@ | sed -e 's/\.po-create$$//'`; \
echo "File $$lang.po does not exist. If you are a translator, you can create it through 'msginit'." 1>&2; \
exit 1
# General rule for updating PO files.
-.nop.po-update:
+%.po-update: %.nop
@lang=`echo $@ | sed -e 's/\.po-update$$//'`; \
if test "$(PACKAGE)" = "gettext-tools" && test "$(CROSS_COMPILING)" != "yes"; then PATH=`pwd`/../src:$$PATH; fi; \
tmpdir=`pwd`; \
--
2.25.0.dirty
next prev parent reply other threads:[~2020-04-01 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 13:12 [PATCH 0/1] old-fashioned suffix rules cannot have any prerequisites Petr Ovtchenkov
2020-04-01 13:12 ` Petr Ovtchenkov [this message]
2020-04-02 0:01 ` Bruno Haible
2020-04-02 1:00 ` Paul Smith
2020-04-02 6:29 ` Petr Ovtchenkov
-- strict thread matches above, loose matches on Subject: below --
2020-04-01 12:26 Petr Ovtchenkov
2020-04-01 12:26 ` [PATCH 1/1] " Petr Ovtchenkov
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200401131254.1330-2-ptr@void-ptr.info \
--to=ptr@void-ptr.info \
--cc=bug-gnulib@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).