Hi Gert,
> >Currently, I don't have the time to take a closer look but if the bug >persists for ITK4.7 I'd suggest to file a bug upstream, and tag #777913 >as "upstream". Anyway, IMHO it is best to wait until 4.7 passes the NEW >queue, then prepare 4.7.2 and check it the bug persists. (I guess you already have the patch :p http://itk.org/gitweb?p=ITK.git;a=commitdiff;h=7f54e864 ) >For itk3.20 it's a bit more complicated, because upstream doesn't>support it >anymore, It would probably be better to file bugs against all >packages that still depend on ITK3.20 and ask to port them (or get new >versions into the archive), and when this is done we could get rid of >this old version altogether. the problem is the same, aka #780659... So many packages should drop non amd64/i386 builds... (no problem for me, maybe itk4 might increase the compatibility archs?) >There is also the issue that gcc-5 uses now by default C11, and I >remember that with -std=C99 ITK4 didn't build, so -std=C11 might bring >up other build failures. exactly I got them after applying the patch on ITK. ../../bin/libITKIO.so.3.20.1: undefined reference to `gdcm::SerieHelper::SetDirectory(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool)' ../../bin/libITKIO.so.3.20.1: undefined reference to `gdcm::SerieHelper::CreateUniqueSeriesIdentifier[abi:cxx11](gdcm::File*)' ../../bin/libITKIO.so.3.20.1: undefined reference to `gdcm::StringFilter::ToString[abi:cxx11](gdcm::Tag const&) const' So I'm wondering if we should just remove it from the archive... (or maybe a gdcm rebuild fixes the issue?) cheers, G. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
