On Tue, 2008-12-16 at 14:48 +0100, Rene Engelhard wrote: > Caesar wrote: > > Furthermore, I notised that the typesconfig crashed during the > > compilation of the module sal because of the qemu fails to support > > something
That's not inherently a problem. typesconfig deliberately finds out what it is allowed or disallowed to do on a given system. As long as it truly is the case that e.g. it is disallowed to access a short on 1-aligned address on your emulated system, then the "crash" is ok. > Build natively. Building natively doesn't have to be a totally horrible experience. e.g. configure and build under qemu-arm, put a distcc client on the qemu-arm, point it as a distcc server on the x86_64 and point the distcc server at the cross compiler. That'll knock a week off the build :-) My understanding is that scratchbox should semi-magically fake an arm environment, set the compiler to be the cross-compiler and use qemu to run any output arm binaries which are executed, so I guess it should work in theory. But I wasn't even able to get scratchbox2 to build hello world when I give it a quick attempt some time ago so I don't think there's anyone with much experience around in building OOo with it. Removing the $ORIGIN lines isn't a great idea. All *might* work ok during the build itself as there's a LD_LIBRARY_PATH in operation then, but after the output has been deployed then ld.so won't be able find the libraries that bits of OOo are linked against, e.g. readelf -d /usr/lib/openoffice.org3/program/soffice.bin |grep ORIGIN Library rpath: [$ORIGIN:$ORIGIN/../basis-link/program:$ORIGIN/../basis-link/ure-link/lib] so for e.g. soffice.bin ldd /path/to/openoffice.org3/program/soffice.bin | grep uno_sal libuno_sal.so.3 => /path/to/openoffice.org3/program/../basis-link/ure-link/lib/libuno_sal.so.3 So libuno_sal.so.3 is found by traversing ../basic-link/ure-link/lib relative to soffice.bin's location. If you cut that out then it won't be able to do that without hacking around with at least a LD_LIBRARY_PATH. C. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
