Following up on my own musings ...

Compiling OO 2.1.0 on a second machine failed. As I use identical 
scripts to build 4 machines (although I do use slightly different 
optimization flags (which are ignored by Openoffice anyway) and although 
the build sequence is not always synchronous, but as long as the 
prerequisites are there in time ...) this was certainly unexpected.

The error was:

/bin/sh ../mkinstalldirs ../data/out ../data/out/build 
../test/testdata/out ../test/testdata/out/build
ICU_DATA=../data/out/build 
LD_LIBRARY_PATH=../common:../i18n:../tools/toolutil:../layout:../layoutex:../extra/ustdio:../tools/ctestfw:../data/out:../data:../stubdata/:$LD_LIBRARY_PATH
 
  ../tools/genpname/genpname -d ../data/out/build
mkdir ../data/out
mkdir ../data/out/build
Error: Unable to create data memory
make[1]: *** [../data/out/build/icudt26l_pnames.icu] Error 1
make[1]: *** Waiting for unfinished jobs....
mkdir ../test/testdata/out
mkdir ../test/testdata/out/build
make[1]: Leaving directory 
`/var/lfs/jim-openoffice-2.1.0/OOE680_m6/icu/unxlngi6.pro/misc/build/icu/source/data'
make: *** [all-recursive] Error 2
dmake:  Error code 2, while making 
'./unxlngi6.pro/misc/build/so_built_so_icu'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making 
/var/lfs/jim-openoffice-2.1.0/OOE680_m6/icu
dmake:  Error code 1, while making 'build_instsetoo_native'
'---*  *---'
Build of openoffice-2.1.0 failed in stage jimMake

I loath these wonderful error messages! Ok, something can go wrong, no 
deal. But I do want to know *what* went wrong in order to get an idea 
for how to fix it. "Unable to create data memory" is just not helpful.
FWIW: The machine in question is a Core2 Due with 2 GiB of RAM and about 
20 GB free space on the filesystem.

The machine where Openoffice built was a Pentium 4 with 512 MiB of RAM 
and 8 GB of free filesystem space. Go figure.

Happy X-Mas anyhow to everybody,
Hans-Joachim
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to