Make & .cshrc

David Elliott dce at mips.COM
Wed Sep 28 00:55:31 AEST 1988


In article <128 at cetia.UUCP> chris at cetia.UUCP (Chris Bertin) writes:
>In article <24946 at ccicpg.UUCP>, nick at ccicpg.UUCP (Nick Crossley) writes:
>> 
>> I personally like this feature/misfeature, as it allows me to invoke ksh.
>
>If 'make' had been modified to get its shell from a different variable (say
>'MAKESHELL', for example), no existing makefiles would have been broken and
>you would still be able to use a different shell. It is a misfeature.

This still doesn't make it.  If I write my makefile such that is requires
sh and you set MAKESHELL to '/bin/csh', there's still a problem.

It's even worse if you are some influential customer of mine and you
decide to force the issue ("Well, things shouldn't break just because
I change my MAKESHELL variable, so you have to fix all 759 makefiles
in your source").

The only obviously correct solution is to say that make defaults to
using sh, and will use an alternate shell if specified in the makefile
itself.  After all, the makefile is written with a shell in mind, so
adding the assignment of SHELL if it's not the default makes the
makefile "self-documenting".

-- 
David Elliott		dce at mips.com  or  {ames,prls,pyramid,decwrl}!mips!dce



More information about the Comp.unix.wizards mailing list