Re: Per-shell override of path names in make(1)

To: tech-toolchain%netbsd.org@localhost
Subject: Re: Per-shell override of path names in make(1)
From: David Holland <dholland-tech%netbsd.org@localhost>
Date: Fri, 8 Feb 2008 05:29:07 +0000

On Thu, Feb 07, 2008 at 09:37:16PM +0100, Joerg Sonnenberger wrote:
 > I don't know. I don't mind removing the csh support completely. I think
 > that happened during the make cleanup in DragonFly.
 > 
 > That would allow to simplify the code quite a bit. It would also raise
 > the question if .SHELL is useful.

Other than to tell make where to find a working sh? I don't think it
is.

The only use for it I can think of is perhaps persuading make to drive
something that isn't a shell at all, like maybe irb or ghci; but that
seems like a fairly crazy undertaking.

-- 
David A. Holland
dholland%netbsd.org@localhost

References:
- Per-shell override of path names in make(1)
  - From: Joerg Sonnenberger
- Re: Per-shell override of path names in make(1)
  - From: Simon J. Gerraty
- Re: Per-shell override of path names in make(1)
  - From: Joerg Sonnenberger

Prev by Date: Re: Per-shell override of path names in make(1)
Next by Date: Re: Per-shell override of path names in make(1)
Previous by Thread: Re: Per-shell override of path names in make(1)
Next by Thread: Re: Per-shell override of path names in make(1)
Indexes:

Home | Main Index | Thread Index | Old Index