From owner-freebsd-current@FreeBSD.ORG Thu Apr 28 05:35:46 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F202A16A4CE for ; Thu, 28 Apr 2005 05:35:46 +0000 (GMT) Received: from april.chuckr.org (april.chuckr.org [66.92.151.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 661FE43D1D for ; Thu, 28 Apr 2005 05:35:46 +0000 (GMT) (envelope-from chuckr@chuckr.org) Received: from [66.92.151.195] (july.chuckr.org [66.92.151.195]) by april.chuckr.org (8.13.1/8.12.11) with ESMTP id j3S5VJO1000962 for ; Thu, 28 Apr 2005 01:31:20 -0400 (EDT) (envelope-from chuckr@chuckr.org) Message-ID: <4270762E.3050508@chuckr.org> Date: Thu, 28 Apr 2005 05:35:42 +0000 From: Chuck Robey User-Agent: Mozilla Thunderbird 1.0 (X11/20050316) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: junk after endif X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2005 05:35:47 -0000 in making the environment for my new sparc box, I'm building a new buildworld for the sparc, that that's giving me REAMS of useless errors about "junk at the end of the line", you know what it is from watching the error come up from cpp listings...except that these come from make, not from C code... having this come up in the situation I'm in, with zero (besides merely a KERNCONF) in the /etc/make.conf, then having this error come up so often it obscures the real listing is egregiously crazy. So, the fix falls into one of these categories: 1) there is a magic incantation I don't know, and don't have time to hunt down, that kills this warning in make, and I need to know this, but that's not the fix ... the fix is (possibly) to make the default action that this is NOT a warning. 2) I know that many folks like to do this to endif's, but it's an warning in C, and we should tell the folks who like it "tough" and take them out. However it's decided, to squish the warning or to squish the tags, it's unacceptable to leave those semantically useless warnings laying about, hiding real problems.