From owner-freebsd-stable Mon Apr 9 9:36:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-32.dsl.lsan03.pacbell.net [63.207.60.32]) by hub.freebsd.org (Postfix) with ESMTP id 34F6C37B423 for ; Mon, 9 Apr 2001 09:36:32 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D948366D3F; Mon, 9 Apr 2001 09:36:30 -0700 (PDT) Date: Mon, 9 Apr 2001 09:36:30 -0700 From: Kris Kennaway To: Matthias Andree Cc: freebsd-stable@FreeBSD.org Subject: Re: BDECFLAGS break current 4.x-stable build Message-ID: <20010409093630.B72961@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ma@dt.e-technik.uni-dortmund.de on Mon, Apr 09, 2001 at 04:09:11PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 09, 2001 at 04:09:11PM +0200, Matthias Andree wrote: > 4.x-stable Checked out today (2001-04-09) at 13:00 UTC > > ***** > NOTE: _ALL_ problems mentioned below disappear with BDECFLAGS removed > from CFLAGS, thus a default build will not encounter these. > ***** Submit patches to fix them, then. BDECFLAGS is there for developers to work on code correctness and possible bugs resulting from language misuse (or general gcc pickiness which doesn't actually involve code bugs). It doesn't change the code generated by gcc. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message