Giuseppe Castagno wrote:
Hi Jan,
Jan Holesovsky wrote:
Hi Giuseppe,
On Wednesday 31 October 2007 22:31, Giuseppe Castagno wrote:
I successfully build from scratch tag SRC680_m235, GNU/Linux Debian
lenny.
Smoketest passed.
Whereas it works all right when installed, I had trouble using linkoo to
symbol link libraries for easier debug.
You have to do 'source ooenv' before you start linkoo-ed OOo - I
believe linkoo warns about it, does it not?
actually I did, it's my preferred method to debug OOo since some time now.
It was ok up to m233, I don't know what was in m234. Now in m235 seems
broken somehow.
No idea what linkoo is and what exactly you mean with "symbol link
libraries," but maybe your problems are related to what I explained to
my colleagues in a Sun-Hamburg-internal mail just yesterday:
"Removing files from the OOo installation's program directory and
replacing them with symbolic links to some build tree (Unix) or adding
some build tree to PATH (Windows) has never worked reliably anyway, and
no longer works at all since SRC680m234:
- On Unix, replacing program/foo.so with a symbolic link to
foo-module/unxlngi6.pro/lib/foo.so for example failed when foo.so needs
bar.so and has an RPATH=$ORIGIN, but bar.so is only present in program,
not in foo-module/unxlngi6.pro/lib.
- Replacing calls to osl_loadModule with just a file name without path
with calls to osl_loadModuleRelative (see
<http://www.openoffice.org/servlets/ReadMsg?list=interface-announce&msgNo=1067>)
means that the calling and the loaded library indeed have to reside in
the same directory.
When you want to use some modified file in an OOo installation, there is
no other reliable way than to physically copy the modified file into the
installation."
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
