[Debian-med-packaging] Bug#826048: Faulty CMake file impairs compiling against GDCM

Peter Mattern pmattern at arcor.de
Wed Jun 1 20:49:39 UTC 2016


Source: gdcm
Version: 2.6.3-{6,5}
Severity: important

Compiling recent Ginkgo CADx against GDCM on Debian stretch yields two cmake warnings which
suggest there are corresponding errors in the packaging of GDCM.

> -- The imported target "vtkgdcmsharpglue" references the file
>   "/usr/lib/x86_64-linux-gnu/libvtkgdcmsharpglue.so"
> but this file does not exist.  Possible reasons include:
> * The file was deleted, renamed, or moved to another location.
> * An install or uninstall procedure did not complete successfully.
> * The installation package was faulty and contained
>   "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
>   but not all the files it references.

libvtkgdcmsharpglue.so is provided by package libvtkgdcm-cil but placed in
/usr/lib/cli/vtkgdcm-sharp-2.6/.

> -- The imported target "vtkgdcmPython" references the file
>   "/usr/lib/python/dist-packages/libvtkgdcmPython.so"
> but this file does not exist.  Possible reasons include:
> * The file was deleted, renamed, or moved to another location.
> * An install or uninstall procedure did not complete successfully.
> * The installation package was faulty and contained
>   "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
>   but not all the files it references.

libvtkgdcmPython.so isn't available any longer in stretch. It used to be provided in jessie
(GDCM 2.4.4) by package python-vtkgdcm in /usr/lib/python2.7/dist-packages/ where a library
libvtkgdcmPython.x86_64-linux-gnu.so can be found in stretch right now.

All findings are the same when the GDCM binary packages of stretch are replaced with their
counterparts from sid plus their additional new or changed dependencies.

The reason to assume it's a packaging issue in Debian is the fact that the warning messages
can not be seen when the same Ginkgo CADx checkout gets compiled against the same GDCM version
on Arch Linux where packaging does not involve any tweaking of GDCM's paths.

On a side note there's by default a bunch of similar messages, see attached ginkgo-vs-gdcm_cmake.txt,
which are simply due to the packages providing the missing files - libvtkgdcm2.6,
libvtkgdcm-java, python-vtkgdcm and libgdcm-tools - not being installed.
Just saying as I'm not sure whether it's alright to not have those files at hand by default.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-------------- next part --------------
-- The imported target "vtkgdcm" references the file
  "/usr/lib/x86_64-linux-gnu/libvtkgdcm.so.2.6.3"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.

-- The imported target "vtkgdcmJava" references the file
  "/usr/lib/x86_64-linux-gnu/jni/libvtkgdcmJava.so"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.

-- The imported target "vtkgdcmPythonD" references the file
  "/usr/lib/x86_64-linux-gnu/libvtkgdcmPythonD.so.2.6.3"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.

-- The imported target "gdcmdump" references the file
  "/usr/bin/gdcmdump"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.

-- The imported target "gdcmdiff" references the file
  "/usr/bin/gdcmdiff"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.

-- The imported target "gdcmraw" references the file
  "/usr/bin/gdcmraw"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.

-- The imported target "gdcmscanner" references the file
  "/usr/bin/gdcmscanner"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.

-- The imported target "gdcmanon" references the file
  "/usr/bin/gdcmanon"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.

-- The imported target "gdcmgendir" references the file
  "/usr/bin/gdcmgendir"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.

-- The imported target "gdcmimg" references the file
  "/usr/bin/gdcmimg"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.

-- The imported target "gdcmconv" references the file
  "/usr/bin/gdcmconv"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.

-- The imported target "gdcmtar" references the file
  "/usr/bin/gdcmtar"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.

-- The imported target "gdcminfo" references the file
  "/usr/bin/gdcminfo"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.

-- The imported target "gdcmscu" references the file
  "/usr/bin/gdcmscu"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.

-- The imported target "gdcmxml" references the file
  "/usr/bin/gdcmxml"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.

-- The imported target "gdcmpap3" references the file
  "/usr/bin/gdcmpap3"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.

-- The imported target "gdcmpdf" references the file
  "/usr/bin/gdcmpdf"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
  "/usr/lib/x86_64-linux-gnu/gdcm-2.6/GDCMTargets.cmake"
  but not all the files it references.


More information about the Debian-med-packaging mailing list