Re: GDCM package: Undefined symbols / VTK misconfiguration

[Dominique Belhachemi <domibel@cs.tu-berlin.de>]

On Mon, 18 May 2009, Mathieu Malaterre wrote:

> I get on the one hand:
>
> $ grep USE_64 ./usr/include/vtk-5.2/vtkConfigure.h
> #define VTK_USE_64BIT_IDS
> $ grep USE_64 usr/lib/vtk-5.2/VTKConfig.cmake
> SET(VTK_USE_64BIT_IDS "ON")
>
> Ok so far so good, VTK was configured with 64 bits ON (thus vtkIdType
> will be 'long long').
>
> BUT on the other hand:
>
>
> $ nm -D ./usr/lib/libvtkCommon.so.5.2.1 | c++filt | grep StringArray::GetVa
> 001ad8c0 T vtkStringArray::GetValue(int)
>
>
> I have never seen that before, I do not even understand how this is
> possible. Are the header files generated on a machine different than
> the binaries files ?

Hi Mathieu,

Thank you for your detailed report.

Maitland added a fix "dev packages now built for each architecture" to 
his git repository one month ago. Your package should work with the 
next upload of VTK. It works at least on my local machine.

Cheers
Dominique