dumping ground for random patches and texts
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: <spew@80x24.org>
Subject: [PATCH] SHELL not /bin/sh
Date: Thu, 22 Dec 2016 22:37:39 +0000	[thread overview]
Message-ID: <20161222223739.22318-1-e@80x24.org> (raw)

---
 configure.in | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/configure.in b/configure.in
index c5132dc97f..ec497408cc 100644
--- a/configure.in
+++ b/configure.in
@@ -721,7 +721,7 @@ mkdir conf$$.dir &&
 (cd conf$$.dir && mkdir src build && cd src &&
 $as_ln_s ../build . > /dev/null 2>&1 && cd build &&
 for chdir in 'cd -P' 'PWD= cd'; do
-    /bin/sh -c "$chdir ../src && echo '$chdir' > cdcmd" 2> /dev/null && break
+    $SHELL -c "$chdir ../src && echo '$chdir' > cdcmd" 2> /dev/null && break
 done)
 if test -f conf$$.dir/src/cdcmd; then
     read CHDIR < conf$$.dir/src/cdcmd 2> /dev/null
@@ -3980,7 +3980,7 @@ fi
 
 AS_CASE("$cross_compiling:${LIBPATHENV}", [yes:* | no:], [], [
     AC_MSG_CHECKING(whether wrapper for $LIBPATHENV is needed)
-    AS_IF([env ${LIBPATHENV}=/lib /bin/sh -c ': ${'${LIBPATHENV}'?}' 2>/dev/null],
+    AS_IF([env ${LIBPATHENV}=/lib $SHELL -c ': ${'${LIBPATHENV}'?}' 2>/dev/null],
 	[AC_MSG_RESULT(no)],
 	[PREP="$PREP"' ruby-runner$(EXEEXT)'
 	AC_MSG_RESULT(yes)]
@@ -4559,7 +4559,7 @@ guard=INCLUDE_RUBY_CONFIG_H
 } | tr -d '\015' |
 (
   if test "x$CONFIGURE_TTY" = xyes; then color=--color; else color=; fi
-  exec ${srcdir}/tool/ifchange $color "${config_h}" -
+  exec $SHELL ${srcdir}/tool/ifchange $color "${config_h}" -
 ) || AC_MSG_ERROR([failed to create ${config_h}])
 tr -d '\015' < largefile.h > confdefs.h
 rm largefile.h
-- 
EW


                 reply	other threads:[~2016-12-22 22:37 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=20161222223739.22318-1-e@80x24.org \
    --to=e@80x24.org \
    --cc=spew@80x24.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).