Hi,
The shared library search paths are set up in the soffice script
right? If so, perhaps the build actually links to a lib in a
"standard" library location for some reason which results in failure
when the OOo local version is used.
What happens when you manually set and export the DYLD_LIBRARY_PATH
to find OOo local libs first and then manually start up soffice.bin?
Does it crash then?
Kevin
On 19-Oct-05, at 2:37 AM, Tino Rachui - Sun Germany - Development -
Software Engineer wrote:
eric.bachard wrote:
Yes, sure. Anyone can test using Panther, and confirm on #i55073# ?
I confirm this issue. Crash on Panther when opening signed documents.
But note the crash just happens when you start OOo using the soffice
script not when you start soffice.bin directly.
More investigation necessary.
Kind regards,
Tino
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
