From owner-freebsd-current Tue May 14 22:35: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from garlic.apnic.net (garlic.apnic.net [202.12.29.224]) by hub.freebsd.org (Postfix) with ESMTP id DAFD137B408 for ; Tue, 14 May 2002 22:35:02 -0700 (PDT) Received: from garlic.apnic.net (localhost [127.0.0.1]) by garlic.apnic.net (8.12.3/8.12.3) with ESMTP id g4F5Z9Tv002633 for ; Wed, 15 May 2002 15:35:09 +1000 (EST) (envelope-from ggm@garlic.apnic.net) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 From: ggm@apnic.net To: current@FreeBSD.ORG Subject: Is current 'safe' to play in again [post GCC changes/stability] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 May 2002 15:35:09 +1000 Message-ID: <2632.1021440909@garlic.apnic.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I held of renewing my make buildworld/installworld state pending the GCC commit. Can I get the sense of the current-users community if its safe to put the toe back in the water? Are there one-time or other headaches one can expect from GCC .so or other objects (the runtime loader/link library handlers?) changing? cheers -George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message