Help ----- OOO300_m9

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Help ----- OOO300_m9

Sheng Huang
Hi people,

All those days, I was trying to cross compile openoffice OOO300_m9, and the
entire procedure functioned pretty well on both x86 and ARM(simulated)
native environments.
However, when I tried to have it compiled on the environment provided by
scratchbox, it failed.
First, it fails because of a glibc bug which relates to the flag
"-rpath,'$ORIGIN'", then I solved it by remove 4 of these flags from the
unxlngr.mk file and 3 other *.mk files under subdirectories of the redland
directory. But my qestion is does this would cause any side effect?
And the next time it fails when it's compiling the udkapi or offapi modules
with the following info.
------------------------------------------------------------

idlc: could not create registry file
'file:///local/ooo-build/ooo-build/build/src680-m175/udkapi/unxlngx6.pro/ucrdoc/com/sun/star/bridge/BridgeExistsException._idlc_'


......

dmake: Error: -- `../unxlngr.pro/ucr/cssawt.db' not found, and can't be made

ERROR: Error 65280 occurred while making /home/caesar/OOo/OOO300_m9/offapi/util


......

dmake: Error: -- `../unxlngr.pro/ucr/cssbridge.db' not found, and can't be made

ERROR: Error 65280 occurred while making /home/caesar/OOo/OOO300_m9/udkapi/util

-------------------------------------------------------------
And the last two messages corresponding to modules offapi and udkapi,
respectively, when it failed, one of this two will pop up.
Sometimes, no error pops up when it's compiling module udkapi and offapi,
but several minutes later, errors pop up and message tells me this:
--------------------------------------------------------------
cc1plus: warning: include location "/usr/include" is unsafe for
cross-compilation
In file included from ../../inc/com/sun/star/uno/Any.h:35,
                 from ../../inc/cppu/helper/purpenv/Mapping.hxx:34,
                 from
/home/caesar/OOo/OOO300_m9/cppu/source/AffineBridge/AffineBridge.cxx:39:
../../inc/com/sun/star/uno/Type.h:35:42: error:
com/sun/star/uno/TypeClass.hdl:No such file or directory
In file included from ../../inc/com/sun/star/uno/Any.h:35,
                 from ../../inc/cppu/helper/purpenv/Mapping.hxx:34,
                 from
/home/caesar/OOo/OOO300_m9/cppu/source/AffineBridge/AffineBridge.cxx:39:
../../inc/com/sun/star/uno/Type.h:99: error: expected `)' before
'eTypeClass'
../../inc/com/sun/star/uno/Type.h:106: error: expected `)' before
'eTypeClass'
../../inc/com/sun/star/uno/Type.h:151: error: 'TypeClass' does not name a
type
In file included from ../../inc/cppu/helper/purpenv/Mapping.hxx:34,
                 from
/home/caesar/OOo/OOO300_m9/cppu/source/AffineBridge/AffineBridge.cxx:39:
../../inc/com/sun/star/uno/Any.h:150: error: 'TypeClass' does not name a
type
dmake:  Error code 1, while making '../../unxlngr.pro/slo/AffineBridge.obj'

ERROR: Error 65280 occurred while making
/home/caesar/OOo/OOO300_m9/cppu/source/AffineBridge
rmdir /tmp/22127
dmake:  Error code 1, while making 'build_instsetoo_native'
--------------------------------------------------------------
Furthermore, I notised that the typesconfig crashed during the compilation
of the module sal because of the qemu fails to support something
---------------------------------------------------------------
char            = unsigned
char
short           = signed
short
int             = signed
int
long            = signed
long
long long               = signed long
long
sizeof(short)           =
2
sizeof(int)             =
4
sizeof(long)            =
4
sizeof(long long)               =
8
sizeof(float)           = 4
sizeof(double)          = 8
sizeof(void *)          = 4
LITTLEENDIAN (Intel, x86-64, PowerPC(LE))
qemu: uncaught target signal 11 (Segmentation fault) - exiting
cannot read address (nil)
qemu: uncaught target signal 11 (Segmentation fault) - exiting
cannot write address (nil)
can read address 0x4007dca4
can write address 0x4007dca4
Access short on 8-Aligned Address : OK
Access short on 4-Aligned Address : OK
Access short on 2-Aligned Address : OK
qemu: uncaught target signal 6 (Aborted) - exiting
Access short on 1-Aligned Address : ERROR
Access int on 8-Aligned Address : OK
Access int on 4-Aligned Address : OK
qemu: uncaught target signal 6 (Aborted) - exiting
Access int on 2-Aligned Address : ERROR
qemu: uncaught target signal 6 (Aborted) - exiting
Access int on 1-Aligned Address : ERROR
Access long on 8-Aligned Address : OK
Access long on 4-Aligned Address : OK
qemu: uncaught target signal 6 (Aborted) - exiting
Access long on 2-Aligned Address : ERROR
qemu: uncaught target signal 6 (Aborted) - exiting
Access long on 1-Aligned Address : ERROR
Access double on 8-Aligned Address : OK
qemu: uncaught target signal 6 (Aborted) - exiting
Access double on 4-Aligned Address : ERROR
qemu: uncaught target signal 6 (Aborted) - exiting
Access double on 2-Aligned Address : ERROR
qemu: uncaught target signal 6 (Aborted) - exiting
Access double on 1-Aligned Address : ERROR
---------------------------------------------------------------

So, can anyone tells me what is going on, and what I need to do to handle
those errors.
Thanks in advance!

Best,

S. Caesar Huang

P.S.:
Info. of my environment:
HOST: x86 Ubuntu 8.10 system
TARGET: ARMv5tel