From owner-freebsd-hackers@FreeBSD.ORG Wed May 28 02:38:03 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9C2237B401 for ; Wed, 28 May 2003 02:38:03 -0700 (PDT) Received: from cirb503493.alcatel.com.au (c18609.belrs1.nsw.optusnet.com.au [210.49.80.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 596E243F93 for ; Wed, 28 May 2003 02:38:02 -0700 (PDT) (envelope-from peterjeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])h4S9bQp9046362; Wed, 28 May 2003 19:37:26 +1000 (EST) (envelope-from jeremyp@cirb503493.alcatel.com.au) Received: (from jeremyp@localhost) by cirb503493.alcatel.com.au (8.12.8/8.12.8/Submit) id h4S9bMxL046361; Wed, 28 May 2003 19:37:22 +1000 (EST) Date: Wed, 28 May 2003 19:37:22 +1000 From: Peter Jeremy To: Julian Elischer Message-ID: <20030528093722.GA46290@cirb503493.alcatel.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: hackers@freebsd.org Subject: Re: gcc problem/openoffice failure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 May 2003 09:38:04 -0000 On Tue, May 27, 2003 at 04:55:47PM -0700, Julian Elischer wrote: >Has anyone been able to compile the openoffice port recently? It built successfully for me on 25th April in -STABLE. Are you using any non-default flags or options? Last time I tried to build it with debugging enabled (beginning of February), it failed (reproducably) inside Mozilla but no-one seemed interested. (The OO maintainer claimed it was a Mozilla problem but that side-stepped the fact that the OO port explicitly over-rides the "no debugging" flags in Mozilla). I know that I previously compiled OO with debugging but it seems that one of the OO or Mozilla upgrades broke it. Peter