From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: reproducing release tarball for 5.0.7
Date: Fri, 10 Oct 2014 11:56:14 +0100 [thread overview]
Message-ID: <20141010115614.7794e14c@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <CAHYJk3QHb9P=tRB1e7dQxey8jMimZ1=v3jaY1-BUGCHncC=nMA@mail.gmail.com>
On Thu, 09 Oct 2014 23:34:20 +0200
Mikael Magnusson <mikachu@gmail.com> wrote:
> So I tried
> % cd Etc
> % make
> cd . && yodl2txt FAQ.yo && mv -f FAQ.txt FAQ
> FAQ.yo:1: Can't read `txt'
> /usr/bin/yodl indicates failure!
> make: *** [FAQ] Error 1
> Makefile:191: recipe for target 'FAQ' failed
>
> Which is a confusing error message.
This works around it if the Yodl installation is fairly standard, though
it's not clear to me it's our job to do so.
Did I miss some much simpler standard Bourne shell way of finding what
directory a command is in?
diff --git a/Etc/Makefile.in b/Etc/Makefile.in
index b6743a7..fed35c7 100644
--- a/Etc/Makefile.in
+++ b/Etc/Makefile.in
@@ -42,11 +42,42 @@ INSTALL = @INSTALL@
all: FAQ
+# Some Yodl installations don't have correct paths to include
+# the standard macros, so find them.
+
FAQ: FAQ.yo
- cd $(sdir) && $(YODL2TXT) FAQ.yo && mv -f FAQ.txt FAQ
+ pathsplit=`echo $$PATH | sed 's%:% %g'`; \
+ include=`for p in $$pathsplit; do \
+ if [ -e $$p/$(YODL2TXT) ]; then \
+ echo $$p | sed -e 's%/bin$$%%'; \
+ break; \
+ fi; \
+ done`; \
+ if [ x$$include != x ]; then \
+ if [ -d $$include/share/yodl ]; then \
+ include="-I$$include/share/yodl"; \
+ else \
+ include=''; \
+ fi; \
+ fi; \
+ cd $(sdir) && $(YODL2TXT) $$include FAQ.yo && mv -f FAQ.txt FAQ
FAQ.html: FAQ.yo
- $(YODL2HTML) $(sdir)/FAQ.yo
+ pathsplit=`echo $$PATH | sed 's%:% %g'`; \
+ include=`for p in $$pathsplit; do \
+ if [ -e $$p/$(YODL2HTML) ]; then \
+ echo $$p | sed -e 's%/bin$$%%'; \
+ break; \
+ fi; \
+ done`; \
+ if [ x$$include != x ]; then \
+ if [ -d $$include/share/yodl ]; then \
+ include="-I$$include/share/yodl"; \
+ else \
+ include=''; \
+ fi; \
+ fi; \
+ $(YODL2HTML) $$include $(sdir)/FAQ.yo
# ========== DEPENDENCIES FOR CLEANUP ==========
pws
--
Peter Stephenson <p.stephenson@samsung.com> Principal Software Engineer
Tel: +44 (0)1223 434724 Samsung Cambridge Solution Centre
St John's House, St John's Innovation Park, Cowley Road,
Cambridge, CB4 0DS, UK
next prev parent reply other threads:[~2014-10-10 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 20:16 Phil Pennock
2014-10-09 20:52 ` Peter Stephenson
2014-10-09 21:34 ` Mikael Magnusson
2014-10-10 9:44 ` Peter Stephenson
2014-10-10 10:56 ` Peter Stephenson [this message]
2014-10-10 6:21 ` Phil Pennock
2014-10-11 0:19 ` Simon Ruderich
2014-10-12 17:00 ` Peter Stephenson
2014-10-13 8:19 ` Phil Pennock
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=20141010115614.7794e14c@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.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).