From owner-freebsd-current Tue Aug 27 18:46:48 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 19D2C37B400 for ; Tue, 27 Aug 2002 18:46:44 -0700 (PDT) Received: from smtpout.mac.com (smtpout.mac.com [204.179.120.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CA8343E72 for ; Tue, 27 Aug 2002 18:46:43 -0700 (PDT) (envelope-from leimy2k@mac.com) Received: from smtp-relay01.mac.com (smtp-relay01-en1 [10.13.10.224]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id g7S1khJ9009804 for ; Tue, 27 Aug 2002 18:46:43 -0700 (PDT) Received: from asmtp01.mac.com (asmtp01-qfe3 [10.13.10.65]) by smtp-relay01.mac.com (8.12.1/8.12.1/1.0) with ESMTP id g7S1kgVw003224 for ; Tue, 27 Aug 2002 18:46:42 -0700 (PDT) Received: from David-Leimbachs-Computer.local ([67.32.249.192]) by asmtp01.mac.com (Netscape Messaging Server 4.15) with ESMTP id H1J69S00.V71; Tue, 27 Aug 2002 18:46:40 -0700 Date: Tue, 27 Aug 2002 20:46:40 -0500 Subject: Re: gcc 3.1 / streambuf.h broken with "using namespace std;" Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v543) Cc: Terry Lambert , freebsd-current@FreeBSD.ORG To: Alexander Langer From: David Leimbach In-Reply-To: <20020828032139.F1412@fump.kawo2.rwth-aachen.de> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.543) 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 is the correct header. This is not a bug On Tuesday, August 27, 2002, at 08:21 PM, Alexander Langer wrote: > Thus spake Terry Lambert (tlambert2@mindspring.com): > >>> What's going on wrong here? >>> GCC 2.9x can compile this, 3.1 cannot: >> Delete and reinstall your header files. They must match >> the compiler you are using, and you must not have stale >> header files from the previous compiler version. > > The -STABLE -> -CURRENT upgrade path is broken then. > >> Use at least GCC 3.2, if you feel compelled to use a buggy >> non-maintenance release level GCC; alternately, wait for 3.3. > > I felt like using -CURRENT's 3.1, as it is expected. > Well, I'll try to look if a new world fixes the problem, though I bet > it > won't. > > Alex > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message