Date: Sun, 11 Sep 2005 22:29:16 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: "David E. O'Brien" <obrien@FreeBSD.org> 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 Message-ID: <20050911222701.W33344@fledge.watson.org> In-Reply-To: <200509071006.j87A6E8s012380@repoman.freebsd.org> References: <200509071006.j87A6E8s012380@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050911222701.W33344>