[Pkg-corba-devel] omniORBpy package issues

[Thomas Girard]

Hello Floris,

Le mercredi 19 décembre 2007 à 23:31 +0000, Floris Bruynooghe a écrit :
> > >  * Lintian also complains about an shlib with non-PIC code
> > >    (_omniConnMgmtmodule.so.3.1).  This has been an issue ever since I
> > >    made the fist python-omniorb2 3.X package and I can't find out why
> > >    (but it doesn't seem to do any harm).  As far as I can tell that
> > >    module gets build in exactly the same way as the other modules, I
> > >    can even see -fPIC in the command line of the build log.  So I'm in
> > >    the dark about this one. 
> > 
> > I'll have a look at these ones. If I can fix these I'll upload omniORBpy
> > 3.1.
> 
> Philipp Kern tried building the package on amd64 and reports that it
> completely breaks building on amd64[0].  So this is actually a serious
> issue which we can't upload with:

[...]

> x86_64-linux-gnu-g++ -shared -Wl,-soname,_omniConnMgmtmodule.so.3 \
>   -o _omniConnMgmtmodule.so.3.1 -L../../lib -L../../../lib -L/usr/lib \
>   pyConnectionMgmt.o -lomniConnectionMgmt4
> /usr/bin/ld: /usr/lib/libomniConnectionMgmt4.a(omniConnectionMgmt.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC
> /usr/lib/libomniConnectionMgmt4.a: could not read symbols: Bad value
> collect2: ld returned 1 exit status
> make[3]: *** [_omniConnMgmtmodule.so.3.1] Error 1

I see it as well on my amd64. It turns out we don't ship
libomniConnectionMgmt4.so.1. (libomniConnectionMgmt4.so is a dangling
symlink.) Therefore g++ tries to use libomniConnectionMgmt4.a, and it
fails to link on amd64 because you cannot mix PIC with non-PIC code.

We'll need another omniorb4 upload :-)

Thanks,

Thomas