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

[Harti Brandt]

On Mon, 9 Aug 2004, John Baldwin wrote:

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

Is that a flash or a ROM? In the first case there is some hope :-)

harti