To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=43074
------- Additional comments from [EMAIL PROTECTED] Fri Feb 18 11:22:27 -0800 2005 ------- Hi, due to integration of pyunofixes1 to m79, it is now the first time, that a python component gets registered during packaging process (a python component is now used for the supporting the scripting framework). So, this probably does not have to do with your patches, this probably has never worked. Please simple try to start python and then type import uno , does this give you the same error ? 'pyuno' is a native python module, it gets loaded by the dynamic load mechanism built into python itself. On 'normal' unixes, it tries to dlopen() a pyuno.so. I guess, the problem is, that in the python runtime, no .dylibs are loaded ? Bye, Joerg --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- 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]
