A couple of comments on the cblfs openoffice 64-bit build -
admittedly using oo-3.0.0...
Ref :
touch external/unowinreg/unowinreg.dll &&
cd config_office/ &&
autoreconf &&
USE_ARCH=64 CC="gcc ${BUILD64}" CXX="g++ ${BUILD64}"
PKG_CONFIG_PATH="${PKG_CONFIG_PATH64}" \
./configure
1. "autoreconf" brings the cpu utilisation up to 100% and never comes
back - omitting this step does seem to cause any problems.
2. despite PKG_CONFIG_PATH="${PKG_CONFIG_PATH64}", dmake fails at
some point with the error that gtk+-2.pc cannot be found in the
pkgconfig path. {PKG_CONFIG_PATH64} is set, but exporting
PKG_CONFIG_PATH=/usr/lib64/pkgconfig fixes the problem.
Ref:
./bootstrap &&
source LinuxX86-64Env.Set.sh
3. Perhaps it's worth mentioning that if you don't have an i686 then
this will be of the form "source Linux-PPC64Env.Set" or similar
Ref:
cd
instsetoo_native/unxlngx6.pro/OpenOffice/native/install/en-US/linux-2.6-x86_64/buildroot/opt
&&
cp -r -v openoffice.org2.4 /opt/openoffice-2.4.1
4. Similar comment to that above for "linux-2.6-x86_64"
Thanks
John
_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
