RE: Cygwin make thinks a statement can be neither true nor false....

%% "Dave Korn" <[EMAIL PROTECTED]> writes: dk> Hmm. So might there be call for a variant of dk> --warn-undefined-variables that only warns about those for which dk> $(origin ..) returns undefined? That way makefiles could supply dk> empty-but-overrideable definitions of CFLAGS etc, and e

RE: Cygwin make thinks a statement can be neither true nor false....

> -Original Message- > From: Paul Smith On Behalf Of Paul D. Smith > Sent: 20 April 2004 19:35 > To: Dave Korn > %% "Dave Korn" writes: > > dk> [ This is getting off topic for the cygwin list, > I'll leave it here for now but I'm happy to re

Re: Cygwin make thinks a statement can be neither true nor false....

Paul D. Smith wrote: %% "Dave Korn" <[EMAIL PROTECTED]> writes: The problem is that in many makefiles you tend to get a lot of "false positives". For example, many makefiles leave certain variables to be set by the user, like CPPFLAGS or CFLAGS. If you do that in your makefiles, and the user has

RE: Cygwin make thinks a statement can be neither true nor false....

%% "Dave Korn" <[EMAIL PROTECTED]> writes: dk> [ This is getting off topic for the cygwin list, and unless I've dk> managed to spot any *real* bugs yet, it's not very OT for the dk> bug-make list either; if we want to carry on further we should dk> perhaps take it to private mail or to the

RE: Cygwin make thinks a statement can be neither true nor false....

> -Original Message- > From: Paul Smith On Behalf Of Paul D. Smith > Sent: 20 April 2004 16:44 [ This is getting off topic for the cygwin list, and unless I've managed to spot any *real* bugs yet, it's not very OT for the bug-make list either; if we want to carry on further we should perh

RE: Cygwin make thinks a statement can be neither true nor false....

%% "Dave Korn" <[EMAIL PROTECTED]> writes: >> I would've expected it to complain about a bad substition reference, >> ie. it's missing an "=". dk> Or at least do anything, rather than nothing! If you enable --warn-undefined-variables then you'll get a warning. dk> Great. So for the b

RE: Cygwin make thinks a statement can be neither true nor false....

> -Original Message- > From: cygwin-owner On Behalf Of Ross Ridge > Sent: 20 April 2004 02:41 [ Cc'd to the gmake bug reporting list; the actual bug report is at the end of this post, and is not what the topic of this thread was originally about. ] > > Possibly a bug in make, as I'd exp

RE: Cygwin make thinks a statement can be neither true nor false....

ECTED] Cc: Subject: RE: Cygwin make thinks a statement can be neither true nor false > Possibly a bug in make, as I'd expect it to complain >about an undefined function named "error:". I would've

RE: Cygwin make thinks a statement can be neither true nor false....

> Possibly a bug in make, as I'd expect it to complain >about an undefined function named "error:". I would've expected it to complain about a bad substition reference, ie. it's missing an "=". > Similar constructs are also silently ignored: > > $(foo This isn't a valid make function) > $(bar

RE: Cygwin make thinks a statement can be neither true nor false....

> -Original Message- > From: cygwin-owner On Behalf Of Robb, Sam > Sent: 19 April 2004 18:57 > > Dave, > > "error:" != "error". You want to use the following > syntax: > > $(error 1 ANYTHING is defined ) > Ach, thanks. I had a space between the 'error' and the ':' everywhere e

RE: Cygwin make thinks a statement can be neither true nor false....

Dave, "error:" != "error". You want to use the following syntax: $(error 1 ANYTHING is defined ) Possibly a bug in make, as I'd expect it to complain about an undefined function named "error:". Similar constructs are also silently ignored: $(foo This isn't a valid make function) $(b