[Debichem-devel] FTBFS openbabel 2.3.0

Michael Banck mbanck at debian.org
Tue Feb 8 10:05:14 UTC 2011


hi,

On Mon, Feb 07, 2011 at 09:25:32AM +0100, Daniel Leidert wrote:
> Hi,
> 
> Anybody familiar enough with CMAKEto resolve this build failure?
> 
> > Linking CXX shared module ../../lib/inchiformat.so
> > cd /tmp/buildd/openbabel-2.3.0/build/src/formats && /usr/bin/cmake -E cmake_link_script CMakeFiles/inchiformat.dir/link.txt --verbose=1
> > /usr/bin/c++  -fPIC -g -O2  -fvisibility=hidden -fvisibility-inlines-hidden -O2 -g -O2 -g -Wl,--enable-new-dtags -Wl,--enable-new-dtags -Wl,--fatal-warnings -Wl,--no-undefined -lc  -shared -Wl,-soname,inchiformat.so -o ../../lib/inchiformat.so CMakeFiles/inchiformat.dir/inchiformat.o CMakeFiles/inchiformat.dir/getinchi.o CMakeFiles/inchiformat.dir/__/ops/unique.o -lm -ldl -lz inchi103/libinchi.a -lm ../../lib/libopenbabel.so.4.0.0 -lc -lm -ldl -lz 
> > /usr/bin/ld: inchi103/libinchi.a(ikey_dll.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
> > inchi103/libinchi.a: could not read symbols: Bad value
> > collect2: ld returned 1 exit status
> > make[4]: *** [lib/inchiformat.so] Error 1
> > make[4]: Leaving directory `/tmp/buildd/openbabel-2.3.0/build'
> > make[3]: *** [src/formats/CMakeFiles/inchiformat.dir/all] Error 2
> 
> I cannot figure how to fix this.

Hrm, maybe that is where I got stuck last time with openbabel-2.3 as
well.  

I think we really don't want to ship a shared libinchi library in the
libopenbabel package.

One possibility would be to start a new source package for inchi, using
the cmake build system from openbabel.  This would allow us to easily
assign a Debian-specific SONAME for libinchi like libinchi.so.0d
(something which I found out to be rather complicated with autotools).

Another option would be to drop inchi support for now.

Or we can try to figure out how to build the static libinchi library
with -fPIC.  

As I am mostly still on 32bit, I am not sure I saw the above error back
then and/or anticipated it and I don't remember whether I tried that or
not.


Michael



More information about the Debichem-devel mailing list