Juli Mallett <[EMAIL PROTECTED]> wrote:
> Why go thru those contortions? I sometimes use "make FOO=" to > define things. -U obviously has a place, if it not existing > means I have to have all these contortions to do a fairly > obvious thing, yeah?
What are the exact semantics of -U supposed to be?
From the message in freebsd-hackers which first introduced this patch:
- Date: Tue, 29 Jul 2003 09:09:17 -0700 - From: Faried Nawaz <[EMAIL PROTECTED]> - Subject: patch to add make -U
While working around a port issue (ports/55013), I discovered
that make couldn't unset variables using make -U. I've written
a small patch that adds -U functionality, but I haven't tested
it extensively.http://web.nilpotent.org/tmp/make.diff.bz2 (~ 3KB unpacked) against yesterday's -CURRENT code.
A simple Makefile I used to test it:
-- cut here --
FOO = bar .ifdef FOO
SAY = y
.else
SAY = n
.endif all:
echo $(SAY)
-- cut here --Try "make -U FOO".
Personally I think this is a reasonable option to implement. An undefined variable is not the same as a variable which is defined to be a null string.
-- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute or [EMAIL PROTECTED] _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
