From owner-freebsd-openoffice@FreeBSD.ORG Mon Nov 10 22:35:49 2014 Return-Path: Delivered-To: openoffice@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 837B01D4 for ; Mon, 10 Nov 2014 22:35:49 +0000 (UTC) Received: from gw.catspoiler.org (cl-1657.chi-02.us.sixxs.net [IPv6:2001:4978:f:678::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 374FE7A5 for ; Mon, 10 Nov 2014 22:35:49 +0000 (UTC) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id sAAMZdXV014396; Mon, 10 Nov 2014 14:35:43 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <201411102235.sAAMZdXV014396@gw.catspoiler.org> Date: Mon, 10 Nov 2014 14:35:39 -0800 (PST) From: Don Lewis Subject: Re: Openoffice-devel build error To: mon.si@gmx.net In-Reply-To: <54614C14.60407@gmx.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: openoffice@FreeBSD.org X-BeenThere: freebsd-openoffice@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting OpenOffice to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2014 22:35:49 -0000 On 10 Nov, Mon Si wrote: > Hello, > > did anybody find a solution for the attached error during the build of > openoffice-devel (en-GB) on FBSD 10.0? > > Any hint is greatly appreciated. > ************************************************** > ERROR: ERROR: unopkg sync --verbose -env:UNO_JAVA_JFW_ENV_JREHOME=true 2>&1 | failed! > in function: register_extensions > ************************************************** > in function: register_extensionsstopping log at Mon Nov 10 05:12:46 2014 > dmake: Error code 255, while making 'openoffice_en-US.archive' Yeah, that looks really familiar. I'm pretty sure it's the --with-system-saxon configure option. The problem is that on FreeBSD 10.x and 11.x, the default system compiler is clang, and it is used to build the saxon port, and brings libc++ along for the ride. The openoffice port is built with a recent version of gcc fromp ports, which causes libstdc++ to be linked in. Those two libraries aren't compatible and cause any executables linked to both to go boom. The existing openoffice-devel port is pretty old (a 4.1.0 development snapshot as I recall). The openoffice port is newer (4.1.1) and doesn't have this problem. If you want to be more bleeding-edge, then you can try the patch to openoffice-devel in this PR , which is a snapshot of the 4.2.0 development.