Path: utzoo!attcan!uunet!husc6!bloom-beacon!gatech!emcard!fedeva!csun!polyslo!cquenel
From: cquenel@polyslo.CalPoly.EDU (Rodent Of Unusual Size)
Newsgroups: comp.unix.wizards
Subject: Re: Make & .cshrc
Message-ID: <4030@polyslo.CalPoly.EDU>
Date: 18 Sep 88 05:47:05 GMT
References: <452@alice.marlow.uucp> <67870@sun.uucp> <67925@sun.uucp> <24946@ccicpg.UUCP> <68801@sun.uucp>
Reply-To: cquenel@polyslo.UUCP (Rodent Of Unusual Size)
Organization: Cal Poly State University -- San Luis Obispo
Lines: 26

In article <68801@sun.uucp> guy@gorodish.Sun.COM (Guy Harris) writes:
>               There is, admittedly, a workaround/fix for this - namely,
>putting "SHELL=/bin/sh" at the beginning of all your makefiles

From a software engineering point of view, ignoring for the moment
what breaks and the inconvenience involved, the above is the most appealing
to me.

each line of a makefile executes "as if the shell executed it" (some shell),
and it makes sense to declare at the top of the Makefile, what program is
to be used as an interpreter for each line.

I am NOT saying "everyone should do this", but it does seem like a safe
thing to do.  I'm also not saying this is an excuse for careless
"make" implementations, just giving my opinion.

(Sheesh, I don't think (Sheesh, I don't thin THAT needs a disclaimer, eh ?)

--chris

-------------------------------------------------------------------------------
| Chris Quenelle            | Smart Mailers -> cquenel@polyslo.CalPoly.EDU    |
| Computer Systems Lab      | Dumb Mailers  -> !ucbvax!voder!polyslo!cquenel  |
| Cal Poly State Univ.      |-------------------------------------------------|
| San Luis Obispo, CA 93407 | /earth is 98% full, please delete anyone you can|
-------------------------------------------------------------------------------