Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ptsfb.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!gamma!epsilon!zeta!sabre!petrus!bellcore!decvax!ittatc!dcdwest!sdcsvax!sdcrdcf!hplabs!qantel!ptsfa!ptsfb!rob
From: rob@ptsfb.UUCP (Rob Bernardo)
Newsgroups: net.unix
Subject: Re: cshell within make
Message-ID: <295@ptsfb.UUCP>
Date: Mon, 13-Jan-86 08:51:38 EST
Article-I.D.: ptsfb.295
Posted: Mon Jan 13 08:51:38 1986
Date-Received: Wed, 15-Jan-86 01:38:10 EST
References: <425@bcsaic.UUCP> <125@idacrd.UUCP>
Reply-To: rob@ptsfb.UUCP (Rob Bernardo)
Organization: Pacific Bell, San Francisco
Lines: 23

In article <125@idacrd.UUCP> wiener@idacrd.UUCP (Matthew P Wiener) writes:
>> This is on BSD 4.2 (on a Sun, v.2.0...)
>> I have several script files written in csh syntax that perform some tests on
>> files.  I would like to invoke them from within 'make.'  The problem is that
>> make insists on using Bourne shell...this despite the fact that the first line
>> in the script file is #/bin/csh, and it runs in csh fine when it is called
>> interactively.
>
>Have your system manager recompile make: somewhere in the source is a
>line that checks your environmental variable $SHELL.  For some reason
>that line is usually commented out, even in BSD.
>

Once I had the "opposite" problem. I was using csh(1) as my login shell,
but the Makefile I often used required use of sh(1). I added the variable
definition

SHELL=/bin/sh

to the Makefile. This way, only the shell used by make(1) was affected,
leaving the environment of my login shell alone. This may be a different
version of make(1) than on the Sun/BSD 4.2, though, being something of a
SYSV Unix(tm) on a Convergent Technologies MegaFrame(tm).