Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: Cygwin make thinks a statement can be neither true nor false.... Date: Mon, 19 Apr 2004 19:13:23 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <3D848382FB72E249812901444C6BDB1DE4E085@exchange.timesys.com> Message-ID: X-OriginalArrivalTime: 19 Apr 2004 18:13:23.0984 (UTC) FILETIME=[00FE4900:01C4263A] > -----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 else I've been using it like that, but I forgot this time, and suddenly couldn't work out what was going wrong. > 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) > $(bar Neither is this) > > -Samrobb Yeh. And when it can't find an include file, I'd like it to complain, rather than just silently add it to a list of missing dependencies, then get to the end of the file and only complain about the first missing dependency. As it stands I can't see any difference between using "-include" and "include". gmake needs a LOT of work in the emission-of-useful-and-accurate-diagnostics department. All too often it just silently does nothing without explaining why, and the only choice you get is that or a million tons of debugging output which doesn't usually contain any useful information whatsoever about what make is actually doing and why. Gah! cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/