From owner-freebsd-mozilla@FreeBSD.ORG  Fri Oct  3 10:25:57 2003
Return-Path: <owner-freebsd-mozilla@FreeBSD.ORG>
Delivered-To: freebsd-mozilla@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 49B0516A4B3
	for <mozilla@freebsd.org>; Fri,  3 Oct 2003 10:25:57 -0700 (PDT)
Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C39C643FDF
	for <mozilla@freebsd.org>; Fri,  3 Oct 2003 10:25:56 -0700 (PDT)
	(envelope-from peterh@sapros.com)
Received: from wartch.sapros.com (sapros.com[12.233.124.48])
          by comcast.net (rwcrmhc11) with ESMTP
          id <2003100317255401300m1mine>; Fri, 3 Oct 2003 17:25:54 +0000
Received: from wartch.sapros.com (localhost [127.0.0.1])
	by wartch.sapros.com (8.12.9p2/8.12.9) with ESMTP id h93HPGmD008182;
	Fri, 3 Oct 2003 10:25:37 -0700 (PDT)
	(envelope-from peterh@sapros.com)
Message-Id: <200310031725.h93HPGmD008182@wartch.sapros.com>
To: Christoph Kukulies <kuku@physik.rwth-aachen.de>
Date: Fri, 03 Oct 2003 10:25:16 -0700
From: Peter Haight <peterh@sapros.com>
cc: mozilla@freebsd.org
Subject: Re: C++ errors in latest builds 
X-BeenThere: freebsd-mozilla@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Mozilla browser issues <freebsd-mozilla.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mozilla>,
	<mailto:freebsd-mozilla-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mozilla>
List-Post: <mailto:freebsd-mozilla@freebsd.org>
List-Help: <mailto:freebsd-mozilla-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mozilla>,
	<mailto:freebsd-mozilla-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Oct 2003 17:25:57 -0000


> Anyone having built mozilla recently? I'm getting a lot off errors of the
> following kind:

I've been getting those too. I read about this in freebsd-current some and
it looks like it might be some combination of libstc++ headers not matching
the compiler and a change in the what -pedantic means to g++. I've gone into
config/autoconf.mk and removed -pedantic from the compiler flags and managed
to get past the place where it was stopping. Still building, though, so
we'll see.