Problem building Openoffice 3.2.0 at current
KOT MATPOCKuH
matpockuh at gmail.com
Mon Mar 1 13:54:52 UTC 2010
Hello!
I'm trying to build OOo 3.2.0 on my notebook with 2Gb of memory and 4Gb swap
size.
from dmesg.boot:
real memory = 2147483648 (2048 MB)
avail memory = 2089287680 (1992 MB)
swapinfo:
Device 1K-blocks Used Avail Capacity
/dev/gpt/swap 4194304 0 4194304 0%
uname -a:
FreeBSD kot 9.0-CURRENT FreeBSD 9.0-CURRENT #40: Wed Feb 10 01:36:25 MSK
2010 root at kot:/usr/obj/usr/src/sys/kot i386
and build fails with messages:
[skipped]
Successful packaging process!
***********************************************************
... creating log file log_OOO320_en-US.log
... creating "follow me" info file follow_me_OOO320_en-US.log.
******************************************
... creating download installation set ...
******************************************
*... including installation set into
/var/ports/usr/ports/editors/openoffice.org-3/work/OOO320_m12/instsetoo_native/
unxfbsdi.pro/OpenOffice_SDK/bsd/install/en-US_download_inprogress/OOo-SDK_3.2.0__install_en-US.sh...
*
*Out of memory during request for 788 bytes, total sbrk() is 96739328 bytes!
*
... checking log file
/var/ports/usr/ports/editors/openoffice.org-3/work/OOO320_m12/instsetoo_native/
unxfbsdi.pro/OpenOffice_SDK/bsd/logging/en-US/log_OOO320_en-US.log
***********************************************************
Successful packaging process!
***********************************************************
... creating log file log_OOO320_en-US.log
dmake: Error code 1, while making 'sdkoo_en-US.bsd'
Running processes: 0
1 module(s):
instsetoo_native
need(s) to be rebuilt
Reason(s):
ERROR: error 65280 occurred while making
/var/ports/usr/ports/editors/openoffice.org-3/work/OOO320_m12/instsetoo_native/util
Attention: if you build and deliver the above module(s) you may prolongue
your the build issuing command "build --from instsetoo_native"
rmdir /tmp/fyA74vD5zg
*** Error code 1
Stop in /usr/ports/editors/openoffice.org-3.
Why I have "out of memory" error and how can I fix this problem?
--
MATPOCKuH
More information about the freebsd-current
mailing list