[Debian-med-packaging] Bug#768769: Please help: failed build of plastimatch 1.5.16+dfsg-2 for several architectures

Dmitry Shachnev mitya57 at gmail.com
Thu Nov 13 11:51:48 UTC 2014


Hi Andreas,

TL;DR: insighttoolkit needs binNMU on !ppc64el.

On Thu, 13 Nov 2014 10:07:16 +0100, Andreas Tille wrote:
> I noticed that the proposed fix does not help to build plastimatch - at
> least the build fails on most architectures[1].

The failing reason in the build log is:

| CMake Error at /usr/lib/InsightToolkit/UseITK.cmake:81 (MESSAGE):
|   ITK was built with GDCM from "/usr/lib/gdcm-2.4", but this project is using
|   GDCM from "/usr/lib/arm-linux-gnueabihf/gdcm-2.4".  Please set GDCM_DIR to
|   match the one used to build ITK.

This is because GDCM recently (on 2014-09-30) switched to multi-arch location [1],
and insighttoolkit (3.x) has NOT been rebuilt against that (the last insighttoolkit
upload is dated 2014-03-09).

[1]: http://anonscm.debian.org/viewvc/debian-med?view=revision&revision=18115

So I guess we need to binNMU insighttoolkit, and the builds will be magically
fixed.

The reason the build succeeded on three archs is that on amd64 and i386
plastimatch uses insighttoolkit4 (which is not affected), and on ppc64el
insighttoolkit was built against new GDCM (ppc64el build was held on 2014-10-15).

> I have the suspicion that simply dropping --parallel from rules
> could solve the issue but it can perfectly be some different problem.

No, that is unrelated and will not help.

--
Dmitry Shachnev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20141113/d583a57a/attachment.sig>


More information about the Debian-med-packaging mailing list