cvs commit: src/usr.bin/make Makefile main.c nonints.h var.c

[John Baldwin]

On Monday 09 August 2004 02:51 pm, Harti Brandt wrote:
> On Mon, 9 Aug 2004, John Baldwin wrote:
>
> JB>On Monday 09 August 2004 11:54 am, Harti Brandt wrote:
> JB>> On Mon, 9 Aug 2004, M. Warner Losh wrote:
> JB>>
> JB>> MWL>In message: <20040809.092824.11587387.imp at bsdimp.com>
> JB>> MWL>: The current man page is stunningly vague about this.  It says
> that it JB>> MWL>: respects these environment variables, but it doesn't say
> they have to JB>> MWL>: be set in the enviornment to the exclusion of
> setting them on the JB>> MWL>: command line.
> JB>> MWL>
> JB>> MWL>So either we can make it work, or document that the variables
> listed JB>> MWL>in the environment section must be set as environment
> variables only. JB>>
> JB>> There is nothing to be made work. Both variables are intended to be
> used JB>> as environment variables. That they happend to work from the
> command line JB>> was a side effect of make putting its variables into the
> environment. JB>> Does the following clarify things enough?
> JB>
> JB>Doesn't change the fact that it can break existing scripts.  I typically
> do JB>
> JB>% worldloop -j 64 MAKEOBJDIRPREFIX=/usr/obj.test
> JB>
> JB>on my test boxes (worldloop is a script that does a 'make buildworld
> "$@"' in JB>a loop).  Can't be fixed I guess.
>
> Wouldn't
>
> MAKEOBJDIRPREFIX=/usr/obj.test worldloop -j 64

^^ env

(I'm a tcsh user).  It will work, but the other one is already programmed into 
my brain. :-/

-- 
John Baldwin <jhb at FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org