From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 32423@debbugs.gnu.org
Subject: bug#32423: 27.0.50; Compilation fails when sh points to zsh
Date: Sat, 11 Aug 2018 20:42:54 +0300 [thread overview]
Message-ID: <83ftzklrz5.fsf@gnu.org> (raw)
In-Reply-To: <87woswlsnc.fsf@calancha-pc.dy.bbexcite.jp> (message from Tino Calancha on Sun, 12 Aug 2018 02:28:23 +0900)
> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Sun, 12 Aug 2018 02:28:23 +0900
>
>
> I started to suffer this recently (~ since this month).
> When
> bin/sh points to /bin/zsh
>
> I get an zsh parse error as follows:
>
> make[2]: Entering directory '/home/calancha/soft/emacs-master/admin/grammars'
> make[2]: Nothing to be done for 'all'.
> make[2]: Leaving directory '/home/calancha/soft/emacs-master/admin/grammars'
> zsh:8: parse error near `done'
> make[2]: Entering directory '/home/calancha/soft/emacs-master/leim'
> make[2]: Nothing to be done for 'all'.
> make[2]: Leaving directory '/home/calancha/soft/emacs-master/leim'
> Makefile:338: recipe for target 'compile-clean' failed
In the marked line:
compile-clean:
@cd $(lisp) && \
elcs=`echo "${SUBDIRS_REL} " | sed -e 's|/\./|/|g' -e 's|/\. | |g' -e 's| |/*.elc |g'`; \
for el in `echo $$elcs | sed -e 's/\.elc/\.el/g'`; do \
if test -f "$$el" || test ! -f "$${el}c"; then :; else \
echo rm "$${el}c"; \
rm "$${el}c"; \
fi \ <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
done
there should be a semi-colon after "fi", I believe. If you make that
change, does the problem go away for you?
next prev parent reply other threads:[~2018-08-11 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-11 17:28 bug#32423: 27.0.50; Compilation fails when sh points to zsh Tino Calancha
2018-08-11 17:42 ` Eli Zaretskii [this message]
2018-08-12 8:30 ` Tino Calancha
2018-08-13 9:58 ` Tino Calancha
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=83ftzklrz5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32423@debbugs.gnu.org \
--cc=tino.calancha@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.