From owner-freebsd-openoffice@FreeBSD.ORG  Wed Sep  3 16:09:30 2008
Return-Path: <owner-freebsd-openoffice@FreeBSD.ORG>
Delivered-To: freebsd-openoffice@FreeBSD.org
Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by hub.freebsd.org (Postfix) with ESMTP id 7E5C41069684;
	Wed,  3 Sep 2008 16:09:30 +0000 (UTC)
	(envelope-from jkim@FreeBSD.org)
From: Jung-uk Kim <jkim@FreeBSD.org>
To: freebsd-openoffice@FreeBSD.org
Date: Wed, 3 Sep 2008 12:09:19 -0400
User-Agent: KMail/1.6.2
References: <2734736F-75E4-42D5-9FD2-7E379140C3D5@laissus.fr>
	<48BD941E.1060406@chillt.de>
In-Reply-To: <48BD941E.1060406@chillt.de>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200809031209.21786.jkim@FreeBSD.org>
Cc: =?iso-8859-1?q?Fran=E7ois_Laissus?= <fr.laissus@laissus.fr>
Subject: Re: Build OpenOffice 3 on FreeBSD 7.0p3 broken ?
X-BeenThere: freebsd-openoffice@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting OpenOffice to FreeBSD <freebsd-openoffice.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-openoffice>, 
	<mailto:freebsd-openoffice-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-openoffice>
List-Post: <mailto:freebsd-openoffice@freebsd.org>
List-Help: <mailto:freebsd-openoffice-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-openoffice>, 
	<mailto:freebsd-openoffice-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Sep 2008 16:09:30 -0000

On Tuesday 02 September 2008 03:29 pm, Bartosz Fabianowski wrote:
> > ERROR: error 65280 occurred while making
> > /usr/ports/editors/openoffice.org-3/work/BEB300_m3/libxml2
> > ERROR: error 65280 occurred while making
> > /usr/ports/editors/openoffice.org-3/work/BEB300_m3/freetype
>
> I have no idea what 65280 means (Google has no idea either), but I
> got the same error code for module binfilter. In my case,
> increasing swap space solved it as the build had simply run out of
> memory (more than 2GB, it's amazing just how much memory OOo needs
> to build). Maybe it's an out of memory issue for you as well?

Actually it is a GCC 4.2 regression and there are many bug reports of 
this type:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12245
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27004
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31863
...

OOo is just another victim.  In fact, we are not alone:

http://bugs.gentoo.org/show_bug.cgi?id=215291

Jung-uk Kim