From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=DMARC_NONE,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=4.0.0 Received: from yatze.fizzelpark.com (yatze.fizzelpark.com [195.94.81.200]) by chiba.3jane.net (Postfix) with SMTP id F1625AC866 for ; Tue, 16 Apr 2002 15:45:14 -0500 (CDT) Received: (qmail 11583 invoked by uid 507); 16 Apr 2002 20:43:11 -0000 Received: from bangert@gentoo.org by yatze by uid 504 with qmail-scanner-1.10 (sophie: 2.7/3.52. . Clear:0. Processed in 0.914631 secs); 16 Apr 2002 20:43:11 -0000 Received: from unknown (HELO there) (212.88.65.169) by mail.fizzelpark.com (195.94.81.201) with SMTP; 16 Apr 2002 20:43:10 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Thilo Bangert To: gentoo-dev@gentoo.org Subject: Re: [gentoo-dev] Something is wrong with my compiler Date: Tue, 16 Apr 2002 22:41:27 +0200 X-Mailer: KMail [version 1.3.2] References: <1018946608.2098.2.camel@davetop> <1018975330.2074.0.camel@davetop> In-Reply-To: <1018975330.2074.0.camel@davetop> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020416204514.F1625AC866@chiba.3jane.net> Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org X-Reply-To: bangert@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: d92a6192-0d4f-4e23-8fbc-f5321a2bfbb7 X-Archives-Hash: dcbc90f404dd9b005d01f4c44a8e03a6 On Tuesday, 16. April 2002 18:42, you wrote: > Does anyone have any ideas on this one? If not, I'm going to file a > bug report. > now, i am no gcc3 expert, but it is known that some stuff (especially c++ projects) don't compile on gcc3... where do you want to file a bugreport? gcc3 is a lot more picky about what it accepts, ie. code must be "more standard compliant"... so either your code is bad or gcc3.1 will (hopefully) fix your problem... hope this helps > --David > -- regards Thilo