Date: Mon, 10 Nov 2014 14:35:39 -0800 (PST) From: Don Lewis <truckman@FreeBSD.org> To: mon.si@gmx.net Cc: openoffice@FreeBSD.org Subject: Re: Openoffice-devel build error Message-ID: <201411102235.sAAMZdXV014396@gw.catspoiler.org> In-Reply-To: <54614C14.60407@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192557>, which is a snapshot of the 4.2.0 development.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201411102235.sAAMZdXV014396>