From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 1/2] Makefile.PL: avoid non-portable $<
Date: Fri, 29 Nov 2019 11:09:13 +0000 [thread overview]
Message-ID: <20191129110914.4306-2-e@80x24.org> (raw)
In-Reply-To: <20191129110914.4306-1-e@80x24.org>
OpenBSD make(1) complains, but FreeBSD make(1) is fine.
---
Makefile.PL | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile.PL b/Makefile.PL
index 4aa0caa7..4d83a198 100644
--- a/Makefile.PL
+++ b/Makefile.PL
@@ -94,7 +94,7 @@ lib/PublicInbox/UserContent.pm :: contrib/css/216dark.css
# Ensure new .pm files will always be installed by updating
# the timestamp of Makefile.PL which forces Makefile to be remade
Makefile.PL : MANIFEST
- touch -r \$< \$@
+ touch -r MANIFEST \$@
\$(PERLRUN) \$@
EOF
next prev parent reply other threads:[~2019-11-29 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 11:09 [PATCH 0/2] minor fixes for OpenBSD make(1) Eric Wong
2019-11-29 11:09 ` Eric Wong [this message]
2019-11-29 11:09 ` [PATCH 2/2] doc: don't attempt to install non-existent manpages Eric Wong
2019-12-01 10:50 ` [PATCH] build: support doc generation w/o GNU make Eric Wong
2019-12-12 8:04 ` [PATCH 2/1] Makefile.PL: fix "dsyn" target Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191129110914.4306-2-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.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).