Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/5/84; site kitty.UUCP Path: utzoo!watmath!sunybcs!kitty!peter From: peter@kitty.UUCP (Peter DaSilva) Newsgroups: net.unix Subject: Re: Re: Failure to execute 'csh'-commands from 'make' Message-ID: <275@kitty.UUCP> Date: Thu, 8-Aug-85 10:31:44 EDT Article-I.D.: kitty.275 Posted: Thu Aug 8 10:31:44 1985 Date-Received: Fri, 9-Aug-85 04:41:39 EDT References: <291@oce-rd1.UUCP> <5433@fortune.UUCP> <824@plus5.UUCP> Organization: Recognition Research Corp., Clarence, NY Lines: 14 > [ihnp4!plus5!hokey] > In article <5433@fortune.UUCP> olson@fortune.UUCP (Dave olson) writes: > >If you have one of the 'augmented' versions of make, S3, S5, (not sure > >how many others...) try setting 'SHELL=/bin/csh'. > > This will, of course, render any bourne shell scripts inoperable, as *all* > shell scripts will be executed by csh. This is pure bs. If your login shell is csh, SHELL=/bin/csh. Csh knows about bourne shell scripts (that begin with anything but a #, or with #!/bin/sh), and calls the bourne shell to execute them. Legend has it that a certain individual who is on the net (and will thus remain nameless) once put a # in front of all the bourne shell scripts on UCBCORY, back when it was "y:". This DID have the effect you suggest.