From owner-freebsd-bugs@FreeBSD.ORG Thu Jul 5 06:00:17 2007 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 26B0116A469 for ; Thu, 5 Jul 2007 06:00:17 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id C4AA813C45D for ; Thu, 5 Jul 2007 06:00:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l6560Gm2039184 for ; Thu, 5 Jul 2007 06:00:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l6560G18039181; Thu, 5 Jul 2007 06:00:16 GMT (envelope-from gnats) Date: Thu, 5 Jul 2007 06:00:16 GMT Message-Id: <200707050600.l6560G18039181@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "Andrew Pantyukhin" Cc: Subject: Re: bin/114082: [make.conf] default CFLAGS have a blank at the end X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andrew Pantyukhin List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2007 06:00:17 -0000 The following reply was made to PR bin/114082; it has been noted by GNATS. From: "Andrew Pantyukhin" To: bug-followup@FreeBSD.org, mi@aldan.algebra.com Cc: Subject: Re: bin/114082: [make.conf] default CFLAGS have a blank at the end Date: Thu, 5 Jul 2007 09:59:48 +0400 So instead of trying to fix this, can we ask why this is a problem at all? We never enforce the absence of extra whitespace in CFLAGS (and almost in any other variable). Cases like "+=" definitions without a preceding "=" definition can easily cause this. Also, having extra blanks before, after or in between flags is valid for almost every application I have seen. AFAIK, this very issue comes from an autoconf idiosyncrasy to match CFLAGS in a broken way and spill out some cache- related errors.