Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: \"special\" shells a security hole?
Message-ID: <5615@brl-smoke.ARPA>
Date: Wed, 11-Feb-87 01:34:30 EST
Article-I.D.: brl-smok.5615
Posted: Wed Feb 11 01:34:30 1987
Date-Received: Thu, 12-Feb-87 04:30:23 EST
References: <3953@brl-adm.ARPA> <2590002@hpisod2.HP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 9

In article <3063@gitpyr.gatech.EDU> robert@gitpyr.UUCP (Robert Viduya) writes:
>Just include "SHELL=/bin/sh" near the beginning of the makefile.

The problem is, you HAVE to do this or you run the risk of having
the Makefile break.  "Make" has no business providing variable
semantics for Makefiles dependent on the user's environment.  I
suppose the original reason for this in Augmented Make was to
permit redefining CC for cross-compilation, etc. without having
to edit zillions of Makefiles.  Too bad SHELL is honored too.