https://bugs.freedesktop.org/show_bug.cgi?id=50682
--- Comment #13 from Stephan Bergmann <[email protected]> 2012-06-22 00:11:43 PDT --- (In reply to comment #11) > I commented the following lines in > /Applications/LibreOffice.app/Contents/MacOS/python: > > DYLD_LIBRARY_PATH=$sd_prog:$sd_prog/../ure-link/lib${DYLD_LIBRARY_PATH:+:$DYLD_LIBRARY_PATH} > export DYLD_LIBRARY_PATH > > import uno does work, and I tested a small number of scripts to validate it's > really working (e.g Hello World from [1]). Ha, right, /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork picking up my LO's /Users/stephan/Desktop/LOdev.app/Contents/MacOS/libsqlite3.dylib instead of the system one as recorded with an installpath in CFNetwork is likely not due to some other LO lib in that process already having loaded LO's libsqlite3.dylib via installpath, but rather due to DYLD_LIBRARY_PATH overriding any recorded installpaths anyway. That means the best fix might be to just replace all mention of DYLD_LIBRARY_PATH in the python script with DYLD_FALLBACK_LIBRARY_PATH (see man page for dyld(1)). Can you try that? (It was likely pure luck that your "small number of scripts" kept working after removing the DYLD_LIBRARY_PATH block completely.) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
