[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

build fail, please help!


i am a LFS user trying desperatly to compile openoffice, but the mail lists 
at openoffice dont seem to give much useful response... i was wondering if 
anyone had any help?

as far as i know LFS and debian are very similar, my system is:
linux 2.4.18
gcc 2.95.3
glibc 2.2.5

here is my method for both 641c and 642:
cd config_office
./configure --with-jdk-home=/usr/lib/java/jdk1.3.1_02 
--prefix=/usr/lib/openoffice --disable-debug
cd ..
mkdir -p solver/641/unxlngi3.pro/inc
touch solver/641/unxlngi3.pro/inc/minormkchanged.flg
edit LinuxIntelEnv.Set to have the correct PATH env set
source LinuxIntelEnv.Set
will probably fail in neon, so delete the neon build tree and reextract the 
source, then run dmake again
dmake install

here are the problems i am getting:
../dist/../cxx/cxx_app.cpp:362: no `int 
DbEnv::set_mutexlocks(int)' member  
function declared in class `DbEnv'
../dist/../cxx/cxx_app.cpp: In method `int 
../dist/../cxx/cxx_app.cpp:362: `struct __db_env' has 
no member named 'set_mutexlocks'
..... and more of the same......
../dist/../cxx/cxx_app.cpp:488: implicit declaration of 
function `int db_env_set_tas_spins(...)'
make: *** [cxx_app.lo] Error 1
dmake:  Error code 2, while making './unxlngi3.pro/misc/build/so_built'
---* TG_SLO.MK *---
ERROR: Error 65280 occurred while making 
dmake:  Error code 1, while making 'build_all'

i have compiled the official releases of database versions 3.2.9 and 4.0.14 
for other purposes with no hassles, its just this version from openooffice 
that gives me problems, and if i substitute the one in the tree with the 
official berkeley release, i get an error later on when building in 
Checking DLL ../unxlngi3.pro/lib/libucpchelp1.so ...: ERROR: 
undefined symbol: cerr

i have also noticed some patching strangeness with the neon component and  
make fails in the auduio code has anyone else experienced this?

any suggestions....

cheers in advance,
"Turn on, tune up, rock out."
-- Billy Gibbons

Reply to: