Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <40856F98.4020605@morganstanley.com> Date: Tue, 20 Apr 2004 14:44:40 -0400 From: Noel Yap Organization: Morgan Stanley User-Agent: Mozilla Thunderbird 0.5 (Windows/20040212) MIME-Version: 1.0 To: "Paul D. Smith" Cc: Dave Korn , cygwin@cygwin.com, bug-make@gnu.org Subject: Re: Cygwin make thinks a statement can be neither true nor false.... References: <16517.17736.2088.461431@lemming.engeast.baynetworks.com> <16517.28015.712309.634072@lemming.engeast.baynetworks.com> In-Reply-To: <16517.28015.712309.634072@lemming.engeast.baynetworks.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Paul D. Smith wrote: > %% "Dave Korn" 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 no reason to set them, then you'll get lots o' warnings. > > You can work around this with various GNU make-specific fanciness, but > most developers don't bother. The largest problem I've seen is when using $(call) on a macro that's not defined (either because the makefile that defines the macro hasn't been included, or there's a typo at the call site). A separate option that would either warn or error upon trying to call undefined macros would be great. What do you think? Noel -- 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/