From owner-freebsd-ports Thu Oct 10 0:43:49 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25F9F37B401 for ; Thu, 10 Oct 2002 00:43:48 -0700 (PDT) Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98E4443EB1 for ; Thu, 10 Oct 2002 00:43:42 -0700 (PDT) (envelope-from parv_fm@mailsent.net) Received: from sdn-ap-020dcwashp0079.dialsprint.net ([63.191.136.79] helo=moo.holy.cow) by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17zXyq-00017B-00; Thu, 10 Oct 2002 00:43:36 -0700 Received: by moo.holy.cow (Postfix, from userid 1001) id A1161BD7F; Thu, 10 Oct 2002 03:46:17 -0400 (EDT) Date: Thu, 10 Oct 2002 03:46:16 -0400 From: parv To: Kris Kennaway Cc: f-ports Subject: Re: is gcc 3.2 port "complete"? Message-ID: <20021010074616.GA52776@moo.holy.cow> Mail-Followup-To: Kris Kennaway , f-ports References: <20021009213907.GA319@moo.holy.cow> <20021010063433.GA6809@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021010063433.GA6809@xor.obsecurity.org> Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org in message <20021010063433.GA6809@xor.obsecurity.org>, wrote Kris Kennaway thusly... > > On Wed, Oct 09, 2002 at 05:39:07PM -0400, parv wrote: > > is this port "complete" as far as "-ansi -pedantic-errors -Wall" > > options are (iow, ANSI/ISO compliance is) concerned? > > Sorry, I have no idea what you're asking. the issue for me is standard C++ programming. the gcc 2.95 included w/ -stable is very sloppy regarding namespace. that is, it doesn't fail to compile the following program, which it should ("-x c++ -ansi -pedantic-errors -Wall" options)... #include <#iostream> int main() { // notice "cout" stream is missing namespace "std" cout << "moo"; return 0; } a few days ago i noticed on -ports list that gcc v3.2 was really gcc v3.1; i was wondering if the gcc32 port is really a v3.2 port. so i asked if lang/gcc32 was a complete (read: real v3.2) standards complaint port. i am sorry if i wasn't clear earlier; doubly so if i have confused even more (people). - parv -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message