From 4f5d97ee9eae6f2adf27e2297f955b601483d61b Mon Sep 17 00:00:00 2001
From: Dan Nicholson <dbn.lists@gmail.com>
Date: Tue, 8 Jul 2008 07:49:31 -0700
Subject: Call minstall with $(SHELL) so the user controls the interpreter

Running minstall directly means that /bin/sh is always used as hte
interpreter. If the user needs or wants to use a different shell fo
minstall, they can use the SHELL make variable.
---
 configs/autoconf.in | 1 -
 configs/default     | 2 +-
 2 files changed, 1 insertion(+), 2 deletions(-)

(limited to 'configs')

diff --git a/configs/autoconf.in b/configs/autoconf.in
index d22c2c5183..8ed1c93d11 100644
--- a/configs/autoconf.in
+++ b/configs/autoconf.in
@@ -31,7 +31,6 @@ SHELL = @SHELL@
 MKLIB_OPTIONS = @MKLIB_OPTIONS@
 MKDEP = @MKDEP@
 MKDEP_OPTIONS = @MKDEP_OPTIONS@
-INSTALL = $(TOP)/bin/minstall
 
 # Python and flags (generally only needed by the developers)
 PYTHON2 = python
diff --git a/configs/default b/configs/default
index 5193c1442d..6c2594b6a9 100644
--- a/configs/default
+++ b/configs/default
@@ -30,7 +30,7 @@ MKLIB_OPTIONS =
 MKDEP = makedepend
 MKDEP_OPTIONS = -fdepend
 MAKE = make
-INSTALL = $(TOP)/bin/minstall
+INSTALL = $(SHELL) $(TOP)/bin/minstall
 
 # Tools for regenerating glapi (generally only needed by the developers)
 PYTHON2 = python
-- 
cgit v1.2.3