openoffice build fails.

[4711 at chello.at]

On Thursday 13 November 2014 10:31:19 Bernt Hansson wrote:
> Hello list.
> 
> FreeBSD 9.3-PRERELEASE #1 r266465
> 
> Trying to build openoffice4 and openoffice-devel.
> Tried libreoffice but then I can not add a printer.
> 
> Oo4 and devel fail at the same place with this:
> 
> ... unopkg sync --verbose -env:UNO_JAVA_JFW_ENV_JREHOME=true 2>&1 | ...
> ... creating links ...
> ... cleaning the output tree ...
> ... removing directory /tmp/ooopackaging/i_148361415810048 ...
> remove_empty_dirs_in_folder
> /usr/ports/editors/openoffice-
devel/work/aoo/main/instsetoo_native/unxfbsdx.
> 
pro/Apache_OpenOffice/archive/install/sv_inprogress/Apache_OpenOffice_4.1.0
_
> FreeBSD_install-arc_sv/openoffice4/share/extensions ... current dir:
> /usr/ports/editors/openoffice-
devel/work/aoo/main/instsetoo_native/unxfbsdx.
> 
pro/Apache_OpenOffice/archive/install/sv_inprogress/Apache_OpenOffice_4.1.0
_
> FreeBSD_install-arc_sv/openoffice4/program ...
> ... unopkg sync --verbose -env:UNO_JAVA_JFW_ENV_JREHOME=true 2>&1 | ...
> ... cleaning the output tree ...
> ... removing directory /tmp/ooopackaging/i_148371415810048 ...
> Error: ERROR: unopkg sync --verbose -
env:UNO_JAVA_JFW_ENV_JREHOME=true
> 2>&1 | failed!
> 
> **************************************************
> 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 Wed Nov 12 17:36:14 2014
> dmake:  Error code 255, while making 'openoffice_en-US.archive'
> 
> 1 module(s):
>          instsetoo_native
> need(s) to be rebuilt
> 
> Reason(s):
> 
> ERROR: error 65280 occurred while making
> /usr/ports/editors/openoffice-devel/work/aoo/main/instsetoo_native/util
> 
> When you have fixed the errors in that module you can resume the build
> by running:
> 
>          build --from instsetoo_native
> 
> *** [do-build] Error code 1
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-
unsubscribe at freebsd.org"


In your case the openoffice-devel port probably uses the previously installed 
libreoffice extensionmanager (unopkg) which resides in /usr/local/bin. 

Renaming the unopkg program 
[# mv /usr/local/bin/unopkg /usr/local/bin/unopkg.bak ]
or deleting the libreoffice package should fix the build of oo-devel.

If you want to use the libreoffice printer-admin-program, it works here on a 9.3-
STABLE system by using this commands:

% cd /usr/local/lib/libreoffice/program
% ./spadmin

On my system libreoffice automatically registered my already configured CUPS-
printer (as oo-devel does).

If both office-packages are installed there are maybe some conflicts when using 
the extensionmanager unopkg. I didn't test this, because i switched to 
libreoffice. libreoffice installs unopkg in /usr/local/bin, openoffice installs it in its 
own /usr/local/openoffice-... path. Maybe there are the same troubles for some 
other files. For a production system I would only install LE or OO, not both.

System: FreeBSD 9.3-STABLE #0 r274469

Ports: %pkg info cups libreoffice apache-openoffice-devel %v
cups-1.7.3_1
libreoffice-4.2.5_5
apache-openoffice-devel-4.1.1560773_4,2

Cheers,