[Debian-med-packaging] Bug#821959: gdcm: FTBFS on hurd, but previously did

[Tobias Frost]

Source: gdcm
Followup-For: Bug #821959

Hi Gert,

I might need your help...
I applied the following patch, but gdcm still insists that it requires 1.7
Is there another place which I need to tweak?

--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -524,8 +524,8 @@
   option(GDCM_USE_JPEGLS "Build GDCM with JPEG-LS support" ON)
   mark_as_advanced(GDCM_USE_JPEGLS)
   if(GDCM_WRAP_JAVA)
-    set(GDCM_JAVA_SOURCE_VERSION "1.7" CACHE STRING "javac source version")
-    set(GDCM_JAVA_TARGET_VERSION "1.7" CACHE STRING "javac target version")
+    set(GDCM_JAVA_SOURCE_VERSION "1.5" CACHE STRING "javac source version")
+    set(GDCM_JAVA_TARGET_VERSION "1.5" CACHE STRING "javac target version")
     mark_as_advanced(GDCM_JAVA_SOURCE_VERSION GDCM_JAVA_TARGET_VERSION)
   endif()
   if(GDCM_WRAP_CSHARP)

Regarding vtk6.3 -- This will its own transition, so I'd appreciate if we could 
clear out vtk5 first..  (vtk is causing some trouble during libpng, so I'd like to 
avoid to entangle them if possible)

Just for the records (your solution is superior), the package buils when
turning off Java support on hurd (of course with adapting the Architecture
field appropiatly)

--
tobi


-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.5-revert-done (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)