[omniORB] Compilation problem gcc2.95.2 omni3.0.2 Solaris2.6

[Harri Pasanen]

At one time I remember that Python link command did not pass the
parameter that exported the symbols from the Python executable to be
used by shared libraries.
But I can't remember which version of Python that was, I just remember
fixing it and even submitting the fix to the Python maintainers.

I can only say that on Solaris 2.7, gcc 2.95.2, Python 2.0 everything
works out of the box.

-Harri


Aleksey Varzhel wrote:
> 
> Well, here is what I got:
> 0009ad24 D _Py_NoneStruct
> I guess, this is Ok.
> 
> I deleted omniORB and Python and compiled them from the very beginning using
> gcc2.95.2
> 
> What can I check else ?
> 
> Thank you for your help.
> 
> Aleksey.
> 
> ----- Original Message -----
> From: "Harri Pasanen" <harri.pasanen@trema.com>
> To: "Aleksey Varzhel" <lesha12@hotmail.com>
> Cc: "Duncan Grisby" <dgrisby@uk.research.att.com>;
> <omniorb-list@uk.research.att.com>
> Sent: Tuesday, January 30, 2001 12:47 AM
> Subject: Re: [omniORB] Compilation problem gcc2.95.2 omni3.0.2 Solaris2.6
> 
> > You can do
> >
> > nm /usr/local/bin/python | grep NoneS
> >
> > You should see something like:
> >
> > 000000000017d514 D _Py_NoneStruct
> >
> > Maybe you didn't compile python with gcc 2.95.2?
> >
> > -Harri
> >
> >
> > Aleksey Varzhel wrote:
> > >
> > > I have compiled Python 1.5.2 and the file mk/platforms/sun4_sosV_5.6.mk
> > > contains a link to /usr/local/bin/python.
> > >
> > > Regarding "stripping" my python executable I am not sure what it is. I'm
> not
> > > familiar with Python and I've installed it to support omniORB only.
> > > Could you advise how I can check if it was stripped ?
> > >
> > > Thank you.
> > >
> > > ----- Original Message -----
> > > From: "Duncan Grisby" <dgrisby@uk.research.att.com>
> > > To: "Aleksey Varzhel" <lesha12@hotmail.com>
> > > Cc: <omniorb-list@uk.research.att.com>
> > > Sent: Monday, January 29, 2001 9:59 AM
> > > Subject: Re: [omniORB] Compilation problem gcc2.95.2 omni3.0.2
> Solaris2.6
> > >
> > > > On Monday 29 January, "Aleksey Varzhel" wrote:
> > > >
> > > > > omniidl: (The error was `ld.so.1: python: fatal: relocation error:
> file
> > > > > /usr/local/omni/lib/sun4_sosV_5.6/_omniidlmodule.so: symbol
> > > _Py_NoneStruct:
> > > > > referenced symbol not found')
> > > >
> > > > That normally happens when you try to use the _omniidl library with a
> > > > different version of Python to the one it was compiled against. Make
> > > > sure that the "python" on your path is the same version of Python as
> > > > the one specified in the mk/platforms/sun4_sosV_5.6.mk file.
> > > >
> > > > Alternatively, have you stripped your python executable?  If so, the
> > > > symbols in it won't be available to the omniidl extension.
> > > >
> > > > Cheers,
> > > >
> > > > Duncan.
> > > >
> > > > --
> > > >  -- Duncan Grisby  \  Research Engineer  --
> > > >   -- AT&T Laboratories Cambridge          --
> > > >    -- http://www.uk.research.att.com/~dpg1 --
> > > >
> > > >
> >
> >

-- 
harri.pasanen@trema.com