tech-toolchain archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

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: Joerg Sonnenberger <joerg%britannica.bec.de@localhost>

Date: Sat, 9 Feb 2008 13:51:35 +0100


On Fri, Feb 08, 2008 at 03:45:22PM +0200, Alan Barrett wrote:
> However, I have never understod why make has built-in knowledge of
> multiple shells.  Why doesn't it just have knowledge of how to drive
> "sh", along with knowledge of where to find the local system's idea of
> a good version of "sh"?  Does anybody actually put ".SHELL: name=ksh"
> or ".SHELL:  name=csh" in Makefiles, and if so, why can't they start
> putting ".SHELL: name=csh path=/wherever/bin/csh foo=bar baz=quux"
> instead?

I agree on this. name=ksh should actually work with name=sh as well,
given that the ksh is new enough. The problem with csh is that it
doesn't support for normal logic for echo and error handling...

Joerg



References:

Per-shell override of path names in make(1)
From: Joerg Sonnenberger

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




Prev by Date: Re: upgrading GCC 4.1 branch

Next by Date: Re: upgrading GCC 4.1 branch

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

Next by Thread: USA Accommodation February 2008

Indexes:

reverse Date

reverse Thread

Old Index



Home | Main Index | Thread Index | Old Index