Kevin B. Hendricks wrote:
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?
Your analysis matches my own expectations. I haven't had the time yet to
check if it is correct.
Anyway
thanks for your analysis.
Kind regards,
Tino
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
