From owner-freebsd-current@FreeBSD.ORG Mon May 14 21:03:21 2007 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6963A16A402 for ; Mon, 14 May 2007 21:03:21 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 5928813C43E for ; Mon, 14 May 2007 21:03:21 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id C3EFB1A3C19 for ; Mon, 14 May 2007 14:04:10 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A8A68514F8; Mon, 14 May 2007 17:03:18 -0400 (EDT) Date: Mon, 14 May 2007 17:03:18 -0400 From: Kris Kennaway To: current@FreeBSD.org Message-ID: <20070514210318.GA5865@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cNdxnHkX5QqsyA0e" Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Cc: Subject: HEADS UP: gcc 4.2 import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2007 21:03:21 -0000 --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline FYI, kan@ is planning to import the gcc 4.2 compiler tomorrow night. This has been through *lots* of testing so it should hopefully be pretty straightforward (as far as major changes go), but there is always the possibility of undetected bugs. It will cause a lot of package builds to fail (about 500-600 depending on architecture). Chances are if you are the maintainer of such a port you have received one or more emails from me about it over the past 6 months. It is not strictly necessary to rebuild your ports after making world with the new compiler, but new binaries may require it since they will be linked to a mixed set of libraries. Besides, the conjunction of symbol versioning, gcc 4.2 and xorg 7.2 means that you'll most likely have to recompile everything anyway - I recommend waiting until the xorg 7.2 import takes place and using precompiled packages when they become available (i.e. portupgrade -faP). We have tried to time the conjunction of these events as best we could to avoid multiple disruptions to -current users, but there will still be a short delay as we wait for more ports committers to test the xorg upgrade before unleashing it on CVS. If you are a ports committer and have not yet reported your build results: we are all waiting for you. ia64 will require some catch-up kernel work to become functional after the import, due to what seems to be missing emulation of some new features used by gcc 4.2. Kris --cNdxnHkX5QqsyA0e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGSM5XWry0BWjoQKURAkfcAKDXj94Rq/Aj7A7AB2LfZmvmg3DczwCfdLWN jTfXsm6/9qh2FKr8Lb4ctFg= =F5E+ -----END PGP SIGNATURE----- --cNdxnHkX5QqsyA0e--