[omniORB] Omniidl and omniidlrun.py problem

[Paulo]

Thanks, I've looked into omniidlrun.py , and it was executing '/usr/bin/env
python', and because i had not set PATH= /usr/local/pythondir it wasn't
working.
The problem you refer (not knowing it is cross-compiling and trying to
execute ,in solaris , the created lynx excutables) happens now. It tries to
execute ../../../bin/powerpc_lynx0s3.0.1/opmkdepend and it fails. To compile
omniORB I should use all the tools created by the solaris compilation
(python, omniidl, omkdepend, ...) ?


I have'nt yet successfully cross-compiled for lynxOS, but  I need to know 2
things:
    - which executables should I export to lynx. I have used omniidl from
solaris, and python from solaris, these two should be exported to lynx, or
each time I need them I have to return to solaris?
    - Is there already a  cos event service implementation in the omniORB
3.0.4? I need to use the push model, i have to download something or
implement my own event service?

Thanks,
Paulo

----- Original Message -----
From: "Duncan Grisby" <dgrisby@uk.research.att.com>
To: "Paulo" <paulo.ismenio@lis2.siemens.pt>
Cc: <omniorb-list@uk.research.att.com>
Sent: Friday, August 24, 2001 12:23 PM
Subject: Re: [omniORB] Omniidl and omniidlrun.py problem


On Thursday 23 August, "Paulo" wrote:

> I am trying to cross-compile omniorb3.0.4 to lynx3.0.1 (from sun =
> solaris) and keep getting this errors:
> %../../../bin/powerpc_lynxos_3.0.1/omniidl
> /usr/bin/env: No such file or directory
>
> % ../../../bin/powerpc_lynxos_3.0.1/omniidlrun.py
> /usr/bin/env: No such file or directory

The root of the problem is that the build environment doesn't know you
are cross-compiling. It has built the IDL compiler for your lynxos
platform, but is trying to run it on Solaris. Have a look at
mk/rtems.mk to see how the build for rtems uses a different platform's
IDL compiler.

Having said that, your immediate problem seems to be that your machine
doesn't have the /usr/bin/env command, which is a bit peculiar. You
can avoid that problem by editing omniidlrun.py to directly reference
/usr/local/bin/python or wherever you put Python.

Cheers,

Duncan.

--
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --