Discussion:
[omniORB] _omnipy load problem
charles bartlett
2007-12-29 20:41:40 UTC
Permalink
Attempting to run echo example.

Unzipped omniORBpy-3.1-x86-win32-python2.5.zip and
omniORB-4.1.1-x86-win32-vc8.zip to windows box with python 2.5.1 loaded.

in python, attempt: "import omniORB"

error message - "import _omnipy
ImportError: DLL load failed: The specified module could not be found."

sys.path includes the directory containing _omnipy; the error message is
misleading - _omnipy is apparently found but can't be read.

Noted <many> similar problems reported in mail; fix answers refer to
incompatible versions of omniORB and python; in my case, should not be
incompatible.

Suggestions?

Thanks.
Duncan Grisby
2007-12-29 21:19:26 UTC
Permalink
Post by charles bartlett
Attempting to run echo example.
Unzipped omniORBpy-3.1-x86-win32-python2.5.zip and
omniORB-4.1.1-x86-win32-vc8.zip to windows box with python 2.5.1 loaded.
in python, attempt: "import omniORB"
error message - "import _omnipy
ImportError: DLL load failed: The specified module could not be found."
sys.path includes the directory containing _omnipy; the error message is
misleading - _omnipy is apparently found but can't be read.
To use omniORBpy, you _just_ need omniORBpy-3.1-x86-win32-python2.5.zip
You should not use the omniORB 4.1.1 distribution at all. If you do
install it, you must put it somewhere unrelated and make sure it is not
on your path.

It sounds like you need to put the omniORBpy binary directory on your
path. Add ...\omniORBpy-3.1\bin\x86_win32 to your path. The _omnipy
module is linked against the omniORB library, and that's what can't be
found.

You are right that the error message is misleading, but it's a message
from Python itself, so omniORBpy can't do anything about it.
Post by charles bartlett
Noted <many> similar problems reported in mail; fix answers refer to
incompatible versions of omniORB and python; in my case, should not be
incompatible.
The similar problem that other people have is that they get conflicts
when running omniidl. That is due to mixing bits of the omniORB binary
distribution with bits of the omniORBpy distribution. The omniORB
distribution contains a minimal version of Python 1.5.2 which conflicts
with newer versions when used with omniORBpy.

Cheers,

Duncan.
--
-- Duncan Grisby --
-- ***@grisby.org --
-- http://www.grisby.org --
charles bartlett
2007-12-30 02:43:01 UTC
Permalink
Post by Duncan Grisby
Post by charles bartlett
Attempting to run echo example.
Unzipped omniORBpy-3.1-x86-win32-python2.5.zip and
omniORB-4.1.1-x86-win32-vc8.zip to windows box with python 2.5.1 loaded.
in python, attempt: "import omniORB"
error message - "import _omnipy
ImportError: DLL load failed: The specified module could not be found."
sys.path includes the directory containing _omnipy; the error message is
misleading - _omnipy is apparently found but can't be read.
To use omniORBpy, you _just_ need omniORBpy-3.1-x86-win32-python2.5.zip
You should not use the omniORB 4.1.1 distribution at all. If you do
install it, you must put it somewhere unrelated and make sure it is not
on your path.
It sounds like you need to put the omniORBpy binary directory on your
path. Add ...\omniORBpy-3.1\bin\x86_win32 to your path. The _omnipy
module is linked against the omniORB library, and that's what can't be
found.
Problem corrected! I thought the path mod was only needed to run
omniidl.
BTW, I did not need to set LD_LIBRARY_PATH and that appears to apply to
Unix anyway.
BTW, I simply added a omniorb.pth file to c:\python25, rather than mod
PYTHONPATH, containing lib/python and lib/$FARCH. Now, in python: import
sys; sys.path to verify they are there. Only mention for those
from __future__.
Post by Duncan Grisby
You are right that the error message is misleading, but it's a message
from Python itself, so omniORBpy can't do anything about it.
Agreed.
Post by Duncan Grisby
Post by charles bartlett
Noted <many> similar problems reported in mail; fix answers refer to
incompatible versions of omniORB and python; in my case, should not be
incompatible.
The similar problem that other people have is that they get conflicts
when running omniidl. That is due to mixing bits of the omniORB binary
distribution with bits of the omniORBpy distribution. The omniORB
distribution contains a minimal version of Python 1.5.2 which conflicts
with newer versions when used with omniORBpy.
Cheers,
Duncan.
Thanks a lot for your support!

Loading...