From owner-freebsd-ports@FreeBSD.ORG  Wed Oct 27 18:19:13 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 EF63516A4CE
	for <freebsd-ports@freebsd.org>; Wed, 27 Oct 2004 18:19:13 +0000 (GMT)
Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com
	[192.108.102.143])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D7ACA43D46
	for <freebsd-ports@freebsd.org>;
	Wed, 27 Oct 2004 18:19:13 +0000 (GMT)
	(envelope-from wa1ter@myrealbox.com)
Received: from [192.168.0.5] wa1ter [67.119.36.172]
	$ on Novell NetWare	via secured & encrypted transport (TLS);
	Wed, 27 Oct 2004 12:19:13 -0600
Message-ID: <417FE6AF.5090405@myrealbox.com>
Date: Wed, 27 Oct 2004 11:19:27 -0700
From: walt <wa1ter@myrealbox.com>
User-Agent: Mozilla/5.0 (X11; U; DragonFly i386; en-US;
	rv:1.8a3) Gecko/20041012
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-ports@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: mozilla-devel still broken on -STABLE
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2004 18:19:14 -0000

This seems to be a gcc2 problem, since gcc3 doesn't complain:

In file included from nsDeviceContextPS.h:50,
                  from nsDeviceContextPS.cpp:55:
nsFontMetricsPS.h:289: ANSI C++ forbids data member `fontps' with same 
name as enclosing class

I sent an email to the upstream developer who wrote the code, but I've 
not heard anything back yet -- dunno if I will.

Is there a 'standard' way of dealing with this kind of compiler-
specific headache?