[omniORB] problems building omniORB3.0 on OpenVMS.7.2

[Adam Dorosz]

Bruce Visscher wrote:

>
> Note that I haven't tested omniORB 3.0 for OpenVMS 7.2, only OpenVMS 7.1
> (and 7.1-2).  I expect that 7.2 will work, I just haven't tested it.

First of all thanks for quick response.

> switch to Python
> 1.5.2-V007B

I did, it seems to work better, althought there was a problem with building
omni:

Making ALL in [SRC.LIB.OMNIORB2.ORBCORE.SHAREDLIB]...
@[mk]CXXShareableImage.dcl "OMNIORB3_RT.EXE"    "[-]OMNIORB3.OLB"
"omnilib:omni_share.olb/include=omnithread_rt"
"/Thre=(upca,mult)/NoTemplate_prelink/map/full"     "3.0.0"
"[.CXX_REPOSITORY] [lib.OpenVMS_Alpha_7_2]"

Linking OMNIORB3_RT.EXE...
%LINK-W-NUDFSYMS, 9 undefined symbols:
%LINK-I-UDFSYM,         const unsigned long CORBA::ContextList::PR_magic
%LINK-I-UDFSYM,         const unsigned long CORBA::Environment::PR_magic
%LINK-I-UDFSYM,         const unsigned long CORBA::ExceptionList::PR_magic
%LINK-I-UDFSYM,         const unsigned long CORBA::NamedValue::PR_magic
%LINK-I-UDFSYM,         const unsigned long CORBA::DynAny::PR_magic
%LINK-I-UDFSYM,         const unsigned long CORBA::NVList::PR_magic
%LINK-I-UDFSYM,         const unsigned long CORBA::Context::PR_magic
%LINK-I-UDFSYM,         const unsigned long CORBA::Request::PR_magic
%LINK-I-UDFSYM,         const unsigned long CORBA::TypeCode::PR_magic
%MMS-F-ABORT, For target OMNIORB3_RT.EXE, CLI returned abort status:
%X10648268.
%MMS-F-ABORT, For target ALL, CLI returned abort status: %X10EE8034.
%MMS-F-ABORT, For target ALL, CLI returned abort status: %X10EE8034.
%MMS-F-ABORT, For target ALL, CLI returned abort status: %X10EE8034.
%MMS-F-ABORT, For target EXPORT, CLI returned abort status: %X10EE8034.
%MMS-F-ABORT, For target ALL, CLI returned abort status: %X10EE8034.
%MMS-F-ABORT, For target EXPORT, CLI returned abort status: %X10EE8034.
%MMS-F-ABORT, For target ALL, CLI returned abort status: %X10EE8034.
%MMS-F-ABORT, For target EXPORT, CLI returned abort status: %X10EE8034.
%MMS-F-ABORT, For target ALL, CLI returned abort status: %X10EE8034.

, but I found that required constants where located in diffrent
CONSTANTS.CC;1 file than compiled and linked to omniorb3_rt.exe.
After copying definition from
OMNIORB300ROOT:[SRC.LIB.OMNIORB2.DYNAMIC]CONSTANTS.CC to
OMNIORB300ROOT:[SRC.LIB.OMNIORB2.ORBCORE]CONSTANTS.CC;1 error disappeard, all
omni files built well.

But now when I call omniidl I have following error information:

import exceptions' failed; use -v for traceback
Warning!  Falling back to string-based exceptions
'import site' failed; use -v for traceback
Traceback (innermost last):
  File "<string>", line 1, in ?
ImportError: No module named os


I had pythonpath set to :
PYTHONPATH ==
"/dka0/python/python-1_5_2/lib:/dka0/python/python-1_5_2/vms/tools"
now it's set to:
PYTHONPATH ==
"dka0:[python.python-1_5_2.lib],dka0:[python.python-1_5_2.vms.tools]"

What's wrong ? Is this error becouse of pythonpath or I have any other symbol
not set ?

Thanks.
Adam