Date: Fri, 18 Aug 2000 01:34:46 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: "Andrey A. Chernov" <ache@nagual.pp.ru> Cc: Brian Fundakowski Feldman <green@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/make Makefile config.h job.c main.c Message-ID: <Pine.BSF.4.21.0008180131500.1746-100000@besplex.bde.org> In-Reply-To: <20000817191010.A83092@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 17 Aug 2000, Andrey A. Chernov wrote:
> On Thu, Aug 17, 2000 at 12:38:05AM -0400, Brian Fundakowski Feldman wrote:
> > On Thu, 17 Aug 2000, Andrey A. Chernov wrote:
> > > There always was ${SHELL} variable for it present in 'make', isn't ?
> >
> > To be honest, it really doesn't work right. This does, however :) This
> > is a very simple change, anyway; some shells require special handling
> > to set up, etc. If you want to make ${SHELL} work better... =)
>
> Do we want another non-standard feature to be different from the rest of
> the world? F.e. GNU make use ${SHELL} for this purpose too.
>
> What is exactly wrong with ${SHELL} variable? IMHO this worth fixing and
> not worth yet another incompatibility.
${SHELL} is undocumented and doesn't affect `make'. I think it is
intentionally left out. `make' has a .SHELL directive which is
extensively documented in the tutorial but not even mentioned in
the man page.
We certainly don't want a second nonstandard way of doing this.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0008180131500.1746-100000>