After emerge sync, openoffice was shown as a package that needed updating. Emerging openoffice emerge continued for several hours (700Mhz processor), and finaly ended with the following error messages: /var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0.1/build/ooo680-m3/sw/ source/ui/uno dmake: Error code 1, while making '../../../unxlngi4.pro/misc/s_unotxvw.dpcc' dmake: '../../../unxlngi4.pro/misc/s_unotxvw.dpcc' removed. '---* TG_SLO.MK *---' ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-2.0.0/work/ ooo-build-2.0.0.1/build/ooo680-m3/sw/source/ui/uno make: *** [stamp/build] Error 1 + diefunc src_compile 204 2 'Build failed' + local funcname=src_compile lineno=204 exitcode=2 + shift 3 I discovered /var was full when I couldnt load a web page, and started looking for the reason Before compilation of openoffice, there was approx 3.5GB of free space on /var. I cant imagine that it should require that much space to compile. Reproducible: Always Steps to Reproduce: 1. emerge -u openoffice 2. 3. Actual Results: Compilation continues until all space on /var has been used, then exists with errors Expected Results: Successful emerge of openoffice System Spec Pentium 3 700Mhz 384MB RAM Kernel 2.6.13-gentoo-r3
OOo uses a lot of disk space while compiling, unfortunately. There are several approaches to accomodating OOo's build process, notably by expanding the amount of disk space on the partition that the /var/tmp/portage resides on. This disk space requirement could not be considered a bug in OOo, though.
