From: Tanu Kaskinen <tanu.kaskinen@linux.intel.com>
To: zsh-workers@zsh.org
Subject: [PATCH] Doc/Makefile.in: create a dummy zsh.texi if if yodl isn't available
Date: Sat, 20 Sep 2014 14:43:42 +0300 [thread overview]
Message-ID: <1411213422-4085-1-git-send-email-tanu.kaskinen@linux.intel.com> (raw)
This fixes a build failure when yodl isn't available.
---
Doc/Makefile.in | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Doc/Makefile.in b/Doc/Makefile.in
index f4ee0d7..41af4a3 100644
--- a/Doc/Makefile.in
+++ b/Doc/Makefile.in
@@ -119,8 +119,10 @@ texi: $(sdir)/zsh.texi
.PHONY: texi
$(sdir)/zsh.texi: version.yo
- $(YODL) -o $@ -I$(sdir) -w ztexi.yo version.yo zsh.yo; \
- test -f $@
+ case '$(YODL)' in :*) touch $@ ;; *) \
+ $(YODL) -o $@ -I$(sdir) -w ztexi.yo version.yo zsh.yo; \
+ test -f $@ \
+ ;; esac
info: zsh.info
.PHONY: info
--
1.9.3
reply other threads:[~2014-09-20 11:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1411213422-4085-1-git-send-email-tanu.kaskinen@linux.intel.com \
--to=tanu.kaskinen@linux.intel.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).