Date: Fri, 19 Apr 2002 00:20:45 +0400 From: Alex Semenyaka <alexs@ratmir.ru> To: Ruslan Ermilov <ru@FreeBSD.ORG> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: make(1) command-line variables Message-ID: <20020418202045.GA407@snark.ratmir.ru> In-Reply-To: <20020418143101.GC70982@sunbay.com> References: <20020413141834.GA16339@snark.ratmir.ru> <001901c1e2fe$2b64c740$1200a8c0@gsicomp.on.ca> <20020413171226.GD18143@snark.ratmir.ru> <20020418143101.GC70982@sunbay.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi there, On Thu, Apr 18, 2002 at 05:31:01PM +0300, Ruslan Ermilov wrote: >> make VAR=VAL # .MAKEFLAGS is empty >> make -DVAR # .MAKEFLAGS is '-D VAR' > Heh, was looking at this NetBSD commitlog today looking for another > thing. They apparently have this bug fixed as well, in the step 3 > below: :: 3. Variables set via command line, are propagated to child-makes via :: MAKEFLAGS. This behaviour appears to be necessary for POSIX (according :: to the GNU folk anyway). So what will The Right Thing be: - to take ``make'' from NetBSD - to transfer corresponding changes from NetBSD - to re-make my patch (to store the command line variables in MAKEFLAGS, not in the new variable)? Of course, I cannot perform first choice but I can do second or third ones. SY, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020418202045.GA407>