[omniORB] Problems building omniORBpy 2.6 under Linux

[Colin Blackburn]

I'm having problems building omniORBpy 2.6 under Linux (RH8, 2.4.18-14, 
gcc 3.2)  I can build 2.0 but get the same error with 2.4 and 2-latest 
as I do with 2.6 (bar the odd line number). The associated omniORBs 
build okay. The tail of the output from gmake is as follows

g++ -c -O2 -Wall -Wno-unused -fexceptions -DOMNIPY_MAJOR=2 
-DOMNIPY_MINOR=6 -I/usr/local/include 
-I/usr/local/include/omniORB4/internal -I../include/omniORB4/internal 
-I../../include/o
mniORB4/internal -I/usr/local/include/omniORB4/internal -I../include 
-I/usr/local/include -DPYTHON_INCLUDE="<python2.4/Python.h>" 
-DPYTHON_THREAD_INC="<python2.4/pythread.h>" -D__OMNIO
RB4__ -I../stub -D_REENTRANT -I/usr/local/include -fPIC -I. 
-I../../modules -I../include -I../../include -D__OSVERSION__=2 
-D__linux__ -D__x86__ -o pyObjectRef.o ../../modules/pyObject
Ref.cc
cc1plus: warning: changing search order for system directory 
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system 
directory
../../modules/pyObjectRef.cc: In static member function `static PyObject*
    omniPy::createPyPseudoObjRef(CORBA::Object*)':
../../modules/pyObjectRef.cc:289: `omniORBpyPseudoFn' undeclared (first use
    this function)
../../modules/pyObjectRef.cc:289: (Each undeclared identifier is 
reported only
    once for each function it appears in.)
../../modules/pyObjectRef.cc:289: parse error before `=' token
../../modules/pyObjectRef.cc:290: `f' undeclared (first use this function)
make[1]: *** [pyObjectRef.o] Error 1
make[1]: Leaving directory 
`/home/root/packages/omniORB/omniORBpy-2.6/build/modules'
make: *** [all] Error 1


Any ideas (for this C++ numpty)?

Colin