From owner-freebsd-current@FreeBSD.ORG Fri Jun 6 23:57:21 2003 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 D972537B401 for ; Fri, 6 Jun 2003 23:57:21 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B4FE43FBD for ; Fri, 6 Jun 2003 23:57:21 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.9/8.12.9) with ESMTP id h576v0Vm064143; Fri, 6 Jun 2003 23:57:04 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h576v0dM064142; Fri, 6 Jun 2003 23:57:00 -0700 (PDT) Date: Fri, 6 Jun 2003 23:57:00 -0700 From: "David O'Brien" To: Tim Kientzle Message-ID: <20030607065700.GA59525@dragon.nuxi.com> Mail-Followup-To: David O'Brien , Tim Kientzle , current@freebsd.org References: <200306070438.h574cs52049913@cueball.rtp.FreeBSD.org> <3EE16E0F.2050207@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EE16E0F.2050207@acm.org> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.1-BETA Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: current@freebsd.org Subject: Re: Can't build -CURRENT on 4.7 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jun 2003 06:57:22 -0000 On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: > The compiler in 4.7 does not like this: > > -std=gnu99 > > As a result, buildworld of -CURRENT fails > rather early. Committers are not required to support building 5-CURRENT, post 5.0-RELEASE on a 4.7 machine. So this is not grounds to remove the change. However, someone will probably patch the build system to tolerate it.