On Feb 21, 7:12 pm, vlad....@gmail.com wrote:
> First thing I tried is to use the 32bits omniORB that I compiled on
> Redhat (32bits) but then when running the exe "omniidl" I would get
> the error everybody posts about "Could not open IDL compiler module
> _omniidlmodule.so ..."
> So I compiled it myself on Suse (64bits) and got 64bits libraries, I
> can't use them, I need 32bits libraries.
> Then I used manual configuration and added the flags "-m32 -Wa,-32 -
> It started compiling fine but then during the build I get the same
> error when it uses "omniidl":
> ../../../bin/i586_linux_2.0_glibc2.1/omniidl -bcxx -p../../../src/lib/
> omniORB -Wbdebug -Wba -p../../../src/lib/omniORB -Wbdebug -v -
> ComniORB4 ../../../idl/Naming.idl
> omniidl: ERROR!
> omniidl: Could not open IDL compiler module _omniidlmodule.so
> omniidl: Please make sure it is in directory /n/fast/vnicul/
> omniidl: (or set the PYTHONPATH environment variable)
> omniidl: (The error was '/n/fast/vnicul/fix_omniORB2/omniORB-4.1.0/lib/
> i586_linux_2.0_glibc2.1/_omniidlmodule.so: cannot open shared object
> file: No such file or directory')
> How comes ? I compiled it my Suse box and it won't run on it ?
> Do you please have any light to shed on this mystery ?
> Am I following the right track (manual config, add the flags myself) ?
> If I'm not clear, don't hesitate to ask me for clarification.
> Thanks very much for your time.
I have found a solution !!!
I have to point config.mk to python in /usr/local/bin/python and
But there's still a problem left.
The build system creates omniidlrun.py start with
So the build still fails.
So I modify the script, rerun the makefile (make export in src) and it
Because the makefile rewrites that script and ignores my