[Debian-med-packaging] Bug#529193: Bug#529193: gdcm: FTBFS: libvtkgdcm.so.2.0.10: undefined reference to `vtkStringArray::GetValue(long long)'

[Mathieu Malaterre]

On Mon, May 18, 2009 at 12:25 AM, Kurt Roeckx <kurt at roeckx.be> wrote:
> Source: gdcm
> Version: 2.0.10-1
> Severity: serious
>
> Hi,
>
> There was an error while trying to autobuild your package:
>
>> Start Time: 20090517-2124
>
> [...]
>
>> Build-Depends: debhelper (>= 5.0.37.2), python-dev, quilt, python-support (>= 0.3.9), uuid-dev, zlib1g-dev, libexpat1-dev, swig, cmake, libvtk5-dev, python-vtk, libpng12-dev | libpng-dev, libjpeg62-dev, libtiff4-dev, libfreetype6-dev, libopenjpeg-dev, libxext-dev, libxss-dev, libxft-dev, mono-devel (>= 2.0)
>
> [...]
>
>> Toolchain package versions: libc6-dev_2.9-12 linux-libc-dev_2.6.29-4 g++-4.3_4.3.3-10 gcc-4.3_4.3.3-10 binutils_2.19.1-1 libstdc++6_4.4.0-5 libstdc++6-4.3-dev_4.3.3-10
>>
>
> [...]
>
>> [ 97%] Built target gdcm
>> make[3]: Entering directory `/build/buildd-gdcm_2.0.10-1-i386-Bvt0O9/gdcm-2.0.10/debian/build-python2.5'
>> Scanning dependencies of target gdcm2vtk
>> make[3]: Leaving directory `/build/buildd-gdcm_2.0.10-1-i386-Bvt0O9/gdcm-2.0.10/debian/build-python2.5'
>> make[3]: Entering directory `/build/buildd-gdcm_2.0.10-1-i386-Bvt0O9/gdcm-2.0.10/debian/build-python2.5'
>> [ 97%] Building CXX object Utilities/VTK/Applications/CMakeFiles/gdcm2vtk.dir/gdcm2vtk.o
>> Linking CXX executable ../../../bin/gdcm2vtk
>> ../../../bin/libvtkgdcm.so.2.0.10: undefined reference to `vtkStringArray::GetValue(long long)'
>> ../../../bin/libvtkgdcm.so.2.0.10: undefined reference to `vtkDataArrayTemplate<long long>::InsertValue(long long, long long)'
>> ../../../bin/libvtkgdcm.so.2.0.10: undefined reference to `vtkDataArrayTemplate<unsigned short>::WritePointer(long long, long long)'
>> ../../../bin/libvtkgdcm.so.2.0.10: undefined reference to `vtkDataArrayTemplate<unsigned char>::WritePointer(long long, long long)'
>> ../../../bin/libvtkgdcm.so.2.0.10: undefined reference to `vtkDataArrayTemplate<long long>::WritePointer(long long, long long)'
>> ../../../bin/libvtkgdcm.so.2.0.10: undefined reference to `vtkDataArray::InsertTuple3(long long, double, double, double)'
>> ../../../bin/libvtkgdcm.so.2.0.10: undefined reference to `vtkLookupTable::SetNumberOfTableValues(long long)'
>> collect2: ld returned 1 exit status
>> make[3]: *** [bin/gdcm2vtk] Error 1
>> make[3]: Leaving directory `/build/buildd-gdcm_2.0.10-1-i386-Bvt0O9/gdcm-2.0.10/debian/build-python2.5'
>> make[2]: *** [Utilities/VTK/Applications/CMakeFiles/gdcm2vtk.dir/all] Error 2
>> make[1]: *** [all] Error 2
>> make: *** [debian/build-python2.5-stamp] Error 2
>> make[2]: Leaving directory `/build/buildd-gdcm_2.0.10-1-i386-Bvt0O9/gdcm-2.0.10/debian/build-python2.5'
>> make[1]: Leaving directory `/build/buildd-gdcm_2.0.10-1-i386-Bvt0O9/gdcm-2.0.10/debian/build-python2.5'
>> dpkg-buildpackage: failure: debian/rules build gave error exit status 2
>
> A full build log can be found at:
> http://buildd.debian.org/build.php?arch=i386&pkg=gdcm&ver=2.0.10-1

This is not a bug in GDCM. This is a misconfiguration of VTK on Linux/i386.

Reproducible bug can be found here:

https://gdcm.svn.sourceforge.net/svnroot/gdcm/Sandbox/debian-med/vtk/vtkidtype

$ cat testidtype.cxx
...
#include "vtkStringArray.h"

int main()
{
  vtkStringArray *s = vtkStringArray::New();
  s->GetValue( 0 );
  return 0;
}
...

This does not compile anymore with VTK 5.2 package on Linux/i386,
while it used to compile using VTK 5.0 package (this is a regression).

I'll submit the bug on libvtk5-dev.

thanks !
-- 
Mathieu