From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 14:50:40 2003 Return-Path: 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 D8E2837B401 for ; Sun, 29 Jun 2003 14:50:40 -0700 (PDT) Received: from mail.blarg.net (floyd.blarg.net [206.124.128.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F4E443FE3 for ; Sun, 29 Jun 2003 14:50:40 -0700 (PDT) (envelope-from abowhill@blarg.net) Received: from io (dsl-129-176.sea.blarg.net [206.124.129.176]) by mail.blarg.net (Postfix) with SMTP id E40C637E92; Sun, 29 Jun 2003 14:50:39 -0700 (PDT) Message-ID: <01ae01c33e89$46904ed0$0200000a@io> From: "Allan Bowhill" To: "Patrick Hartling" References: <013601c33e6a$eb312d70$0200000a@io> <3EFF308B.6060200@137.org> Date: Sun, 29 Jun 2003 14:56:20 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: fbsd-current Subject: Re: errors under g++ 3.2.2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2003 21:50:41 -0000 > I do a lot of C++ development on -current, and I have been seeing these > exact warnings. The problem is in the fstream header, however, so there > is nothing you can do to your code to prevent the warnings. You could > modify /usr/include/g++/fstream to silence the warnings, but it would > get overwritten if you upgrade your system. Oh good :) I was thinking there was something I needed to add to make the code compliant. > From your output, I don't see compile failures, I see warnings. Do you > have -Werror turned on somewhere that wouldn't show up during normal > usage--like some environment variable or something? I was able to > compile and run your code without issue here. > > Honestly, I am surprised that a GCC header would have an implicit > typename since the compiler clearly complains loudly about them. At any > rate, I think the update to GCC 3.3 in -current is going to happen quite > soon, and presumably, the updated GCC C++ headers will have warnings > such as these fully eliminated. You're right. These are warnings, and it does compile. I guess I got a bit stuck on trying to determine why the messages were occuring. Thanks for your comments. --Allan