From owner-cvs-all@FreeBSD.ORG Sun Sep 11 21:29:18 2005 Return-Path: X-Original-To: cvs-all@FreeBSD.org Delivered-To: cvs-all@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D1DC16A41F; Sun, 11 Sep 2005 21:29:18 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id C49C743D45; Sun, 11 Sep 2005 21:29:17 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id E8B9246B33; Sun, 11 Sep 2005 17:29:16 -0400 (EDT) Date: Sun, 11 Sep 2005 22:29:16 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "David E. O'Brien" In-Reply-To: <200509071006.j87A6E8s012380@repoman.freebsd.org> Message-ID: <20050911222701.W33344@fledge.watson.org> References: <200509071006.j87A6E8s012380@repoman.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_tc.c src/sys/net rtsock.c src/sys/netipx ipx_proto.c src/sys/netnatm natm_proto.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2005 21:29:18 -0000 On Wed, 7 Sep 2005, David E. O'Brien wrote: > Modified files: > sys/kern kern_tc.c > sys/net rtsock.c > sys/netipx ipx_proto.c > sys/netnatm natm_proto.c > Log: > Forward declaring static variables as extern is invalid ISO-C. Now that > GCC can properly handle forward static declarations, do this properly. As a result of this change, it is no longer possible to build 7.x kernels on 6.x worlds without building all of world or tweaking kernel makefiles. While that's not a formally supported configuration, it makes it a lot easier and faster to do development from a central buildbox on a farm of test systems. Given that you've MFC'd the gcc fix to RELENG_5, I assume a change will be queued to merge to RELENG_6, but in the mean time it's something of an irritating problem (up there with NOMAN -> NO_MAN). In the future, could you merge the gcc fixes to the relevant branches before merging the dependent C changes, in order to avoid this sort of thing? Robert N M Watson