[Debian-med-packaging] Bug#614953: gdcm: FTBFS due to recent gcc-4.4 / linker changes

Adam D. Barratt adam at adam-barratt.org.uk
Thu Feb 24 13:34:08 UTC 2011


Package: gdcm
Version: 2.0.16-2
Severity: serious

Hi,

gdcm FTBFS on multiple architectures. From the build logs, this appears to
be due to the recent change in gcc-4.4's invocation of the linker:

Linking CXX executable ../../../bin/gdcm2vtk
/usr/bin/ld: CMakeFiles/gdcm2vtk.dir/gdcm2vtk.cxx.o: undefined reference
to symbol 'gdcm::ImageHelper::SetForceRescaleInterceptSlope(bool)'
/usr/bin/ld: note:
'gdcm::ImageHelper::SetForceRescaleInterceptSlope(bool)' is defined in DSO
/build/buildd-gdcm_2.0.16-2+b1-sparc-oHzEOx/gdcm-2.0.16/debian/build-python2.6/bin/libgdcmMSFF.so.2.0
so try adding it to the linker command line
/build/buildd-gdcm_2.0.16-2+b1-sparc-oHzEOx/gdcm-2.0.16/debian/build-python2.6/bin/libgdcmMSFF.so.2.0:
could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make[3]: *** [bin/gdcm2vtk] Error 1

Full logs available via https://buildd.debian.org/status/package.php?p=gdcm

Regards,

Adam






More information about the Debian-med-packaging mailing list