From owner-freebsd-current Tue Aug 27 18:19:23 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 C638B37B400 for ; Tue, 27 Aug 2002 18:19:21 -0700 (PDT) Received: from fump.kawo2.rwth-aachen.de (fump.kawo2.RWTH-Aachen.DE [134.130.181.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9BF143E3B for ; Tue, 27 Aug 2002 18:19:20 -0700 (PDT) (envelope-from alex@fump.kawo2.rwth-aachen.de) Received: from fump.kawo2.rwth-aachen.de (localhost [127.0.0.1]) by fump.kawo2.rwth-aachen.de (8.12.5/8.12.5) with ESMTP id g7S1LesJ003186; Wed, 28 Aug 2002 03:21:40 +0200 (CEST) (envelope-from alex@fump.kawo2.rwth-aachen.de) Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.12.5/8.12.5/Submit) id g7S1LdRG003185; Wed, 28 Aug 2002 03:21:39 +0200 (CEST) Date: Wed, 28 Aug 2002 03:21:39 +0200 From: Alexander Langer To: Terry Lambert Cc: freebsd-current@FreeBSD.org Subject: Re: gcc 3.1 / streambuf.h broken with "using namespace std;" Message-ID: <20020828032139.F1412@fump.kawo2.rwth-aachen.de> Mail-Followup-To: Alexander Langer , Terry Lambert , freebsd-current@FreeBSD.org References: <20020828021006.D1412@fump.kawo2.rwth-aachen.de> <3D6C1F76.30B458A5@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3D6C1F76.30B458A5@mindspring.com>; from tlambert2@mindspring.com on Tue, Aug 27, 2002 at 05:55:18PM -0700 X-PGP-Fingerprint: 7EC1 5B98 4554 2A63 9079 2B2F 9A94 CD6F 7F14 EFA4 X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. 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 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