Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!gatech!lll-lcc!unisoft!mtxinu!ed
From: ed@mtxinu.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: "make" SHELL variable
Message-ID: <309@mtxinu.UUCP>
Date: Tue, 3-Mar-87 14:05:39 EST
Article-I.D.: mtxinu.309
Posted: Tue Mar  3 14:05:39 1987
Date-Received: Fri, 6-Mar-87 01:40:41 EST
References: <3953@brl-adm.ARPA> <2590002@hpisod2.HP>
Reply-To: ed@mtxinu.UUCP (Ed Gould)
Organization: mt Xinu, Berkeley, CA
Lines: 26

I agree with Guy Harris's assesment of what would be right for make:
to always use /bin/sh, like the old days.

>>It has always been easy enough for me to put 
>>
>>	setenv SHELL /bin/sh
>>
>>in my .login to mollify make.
>
>And possibly confuse other programs that use SHELL to determine which
>shell to use when handling a "shell escape" command - or, more
>likely, confuse the user who tries to use a "shell escape" command.

The workaround I use - that avoids just this side effect - is

	alias	make	make SHELL=/bin/sh

Since variables set on the command line override those from the
environment, this works.  It breaks makefiles that explicitly
assigh tht SHELL variable, though.

-- 
Ed Gould                    mt Xinu, 2560 Ninth St., Berkeley, CA  94710  USA
{ucbvax,decvax}!mtxinu!ed   +1 415 644 0146

"A man of quality is not threatened by a woman of equality."