[Debian-med-packaging] Bug#1042246: gdcm: FTBFS: make[1]: *** [debian/rules:107: override_dh_auto_configure] Error 2

[Aurelien Jarno]

Hi,

On 2023-07-26 22:24, Lucas Nussbaum wrote:
> Source: gdcm
> Version: 3.0.21-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lucas at debian.org
> Usertags: ftbfs-20230726 ftbfs-trixie
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 

I have started to investigate this, but my cmake knowledge is quite
limited, so I am progressing slowly. Here are my findings:

- The issue has been introduced by cmake 3.27. gdcm builds fine with
  cmake from stable and everything else from sid.

- The reported issue seems to be linked to a cache issue between the two
  libexpat detection: the one from gdcm in CMakeLists.txt:423 and using
  find_package() and the one shipped by libvtk9-dev in 
  $DEB_HOST_MULTIARCH/cmake/vtk-9.1/FindEXPAT.cmake: using
  find_library(). Dropping the first one or passing NO_CACHE to
  find_library() is enough to get rid of the issue.

- The issue is only visible with DGDCM_USE_SYSTEM_EXPAT:BOOL=ON which is
  not the default, so it is likely that the issue hasn't been noticed
  before.

- Independently of the reported issue, gdcm still uses find_package()
  with PythonInterp or PythonLibs which have been removed from cmake
  3.27, so fixing it is not enough to get gdcm working.

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien at aurel32.net                     http://aurel32.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/debian-med-packaging/attachments/20230823/771e243a/attachment-0001.sig>