On Mon, 2013-03-18 at 00:56 -0500, Steve M. Robbins wrote: > Hi Paul, > > Just getting back to some ITK work... > > On February 13, 2013 08:21:52 AM Paul Novotny wrote: > > > So, long story short, we should use system tiff > > (-DITK_USE_SYSTEM_TIFF:BOOL=ON) and apply the attached patch. Or, not > > use system tiff and use the patch in [1]. I vote for using system tiff. > > I agree. > > So I turned on system tiff, added your patch, and updated the > build depends. Depending on libtiff5-dev failed due to conflict with libvtk5- > dev, so I used libtiff5-alt-dev instead. I presume you did the same, yes?
Now that I look back, I am not sure what I did. I might still be using libtiff4-dev? But in any case, did libtiff5-alt-dev work? That seems to be the way to go. Anyway I should probably summarize what I have been trying to do lately. Basically, I have been trying to get all the tests to pass on a sparc machine. From what I can tell, most of them have to do with gdcm, and it not working on a big-endian machine. I noticed that gdcm itself is built with testing off, and when you turn it back on, all sorts of tests fail, so that isn't good. Anyway, I will continue to try and make some sense of it. -Paul -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1363704495.5106.40.camel@PaulDesktop
