From owner-freebsd-current Sun Sep 1 12:35:40 2002 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 4518C37B400 for ; Sun, 1 Sep 2002 12:35:38 -0700 (PDT) Received: from warez.scriptkiddie.org (uswest-dsl-142-38.cortland.com [209.162.142.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F8A843E3B for ; Sun, 1 Sep 2002 12:35:37 -0700 (PDT) (envelope-from lamont@scriptkiddie.org) Received: from [192.168.69.11] (unknown [192.168.69.11]) by warez.scriptkiddie.org (Postfix) with ESMTP id BA3B262D1A for ; Sun, 1 Sep 2002 12:35:35 -0700 (PDT) Date: Sun, 1 Sep 2002 12:37:14 -0700 (PDT) From: Lamont Granquist To: freebsd-current@FreeBSD.ORG Subject: Re: gcc 3.1 / streambuf.h broken with "using namespace std;" In-Reply-To: <20020901183043.GF94999@dragon.nuxi.com> Message-ID: <20020901121241.F10365-100000@coredump.scriptkiddie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Sun, 1 Sep 2002, David O'Brien wrote: > 3.3.0 will be released before FreeBSD 5.1. It is my advice to > FreeBSD'ville that we go with a GCC 3.3 snapshot for FBSD 5.0 and a GCC > 3.3.0 release for FBSD 5.1. That way we can get the new features of 3.3 > into our 5.x branch. AND get bug fixes by importing 3.3.1 and 3.3.2 into > later FBSD 5.x releases. 5.0 will be a beta and will not be ready for production use right? If so, it seems perfectly acceptable to use a 3.3 snapshot and risk breaking binary compatibility between 5.0 and 5.1. If it happens, you mention the breakage in UPDATING and people who are using 5.0 should be expected to be paying attention. This way we get to where we want to be, which is 5.2 or 5.3 being a stable operating system with a stable and well-supported compiler. That seems to be the right long-term goal to shoot for. It sounds like gcc-3.1 or gcc-3.2 will be archaic and buggy by the time that 5.2 and 5.3 come out. I'm not sure exactly how FreeBSD would be "pulling a redhat" by putting in a development snapshot if the 5.0 release is clearly labelled for non-production use only... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message