From owner-freebsd-questions@FreeBSD.ORG Mon May 30 15:29:16 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 310D210656E8 for ; Mon, 30 May 2011 15:29:16 +0000 (UTC) (envelope-from griffin@gnix.co.uk) Received: from think.gnix.co.uk (griffin.gnix.co.uk [80.229.5.32]) by mx1.freebsd.org (Postfix) with ESMTP id 915488FC19 for ; Mon, 30 May 2011 15:29:14 +0000 (UTC) Received: from think.gnix.co.uk (localhost [127.0.0.1]) by think.gnix.co.uk (8.14.4/8.14.4) with ESMTP id p4UFTE3J017897 for ; Mon, 30 May 2011 16:29:14 +0100 (BST) (envelope-from griffin@gnix.co.uk) Received: (from jpg@localhost) by think.gnix.co.uk (8.14.4/8.14.4/Submit) id p4UFTDwT017896 for freebsd-questions@freebsd.org; Mon, 30 May 2011 16:29:13 +0100 (BST) (envelope-from griffin@gnix.co.uk) X-Authentication-Warning: think.gnix.co.uk: jpg set sender to griffin@gnix.co.uk using -f Date: Mon, 30 May 2011 16:29:13 +0100 From: Jamie Paul Griffin To: freebsd-questions@freebsd.org Message-ID: <20110530152913.GA17861@think.gnix.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-Key: http://www.gnix.co.uk/~jpg/jpg-pubkey.asc X-Operating-System: FreeBSD 8.2-RELEASE X-URL: http://www.gnix.co.uk/~jpg/ User-Agent: Mutt/1.5.21 (2010-09-15) Subject: editors/openoffice.org-3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 15:29:16 -0000 Hello the build of this port fails due to a problem with the 'moz' module: ERROR: error 65280 occurred while making /usr/ports/editors/openoffice.org-3/work/000330_m20/moz [ ... ] I found a thread sent to freebsd-openoffice@ earlier this month where several people said they had experienced this problem, the last message in it was dated 15 May 2011. No update after and no indication when the problem might be fixed. I wondered if anyone here has any more information about this? best wishes, jamie