Source: nifti2dicom Version: 0.4.11-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170805 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/core && /usr/bin/g++ > -DITK_IO_FACTORY_REGISTER_MANAGER > -DvtkFiltersFlowPaths_AUTOINIT="1(vtkFiltersParallelFlowPaths)" > -DvtkIOExodus_AUTOINIT="1(vtkIOParallelExodus)" > -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" > -DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" > -DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" > -DvtkIOSQL_AUTOINIT="2(vtkIOMySQL,vtkIOPostgreSQL)" > -DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)" > -DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)" > > -DvtkRenderingFreeType_AUTOINIT="2(vtkRenderingFreeTypeFontConfig,vtkRenderingMatplotlib)" > -DvtkRenderingLIC_AUTOINIT="1(vtkRenderingParallelLIC)" > -DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpenGL)" > -I/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/ITKIOFactoryRegistration > -I/usr/include/hdf5/serial -I/usr/include/dcmtk/dcmseg > -I/usr/include/dcmtk/dcmfg -I/usr/include/dcmtk/dcmiod > -I/usr/include/dcmtk/dcmrt -I/usr/include/dcmtk/dcmpstat > -I/usr/include/dcmtk/dcmqrdb -I/usr/include/dcmtk/dcmwlm > -I/usr/include/dcmtk/dcmsign -I/usr/include/dcmtk/dcmsr > -I/usr/include/dcmtk/dcmnet -I/usr/include/dcmtk/dcmtls > -I/usr/include/dcmtk/dcmjpls -I/usr/include/dcmtk/dcmjpeg > -I/usr/include/dcmtk/dcmimage -I/usr/include/dcmtk/dcmimgle > -I/usr/include/dcmtk/dcmdata -I/usr/include/dcmtk/oflog > -I/usr/include/dcmtk/ofstd -I/usr/include/dcmtk/config > -I/usr/include/x86_64-linux-gnu -I/usr/include/nifti -I/usr/include/gdcm-2.6 > -I/usr/include/double-conversion -isystem /usr/include/ITK-4.10 > -I/usr/include/vtk-6.3 -I/usr/include/freetype2 > -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi > -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent > > -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent/include > -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/python2.7 > -I/usr/include/hdf5/openmpi -I/usr/include/libxml2 -I/usr/include/jsoncpp > -I/usr/include/tcl -I/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu -g -O2 > -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time > -D_FORTIFY_SOURCE=2 -o CMakeFiles/nifti2dicom_core.dir/n2dVersion.cxx.o > -c /<<PKGBUILDDIR>>/src/core/n2dVersion.cxx > In file included from /usr/include/ITK-4.10/vcl_limits.h:5:0, > from /usr/include/ITK-4.10/itkNumericTraits.h:51, > from /usr/include/ITK-4.10/itkConceptChecking.h:32, > from /usr/include/ITK-4.10/itkAtomicInt.h:38, > from /usr/include/ITK-4.10/itkLightObject.h:25, > from /usr/include/ITK-4.10/itkObject.h:31, > from /usr/include/ITK-4.10/itkVersion.h:31, > from > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/Nifti2DicomConfig.h:30, > from /<<PKGBUILDDIR>>/src/core/n2dVersion.cxx:21: > /usr/include/ITK-4.10/vcl_compiler.h:79:4: error: #error "Dunno about this > gcc" > # error "Dunno about this gcc" > ^~~~~ > In file included from /<<PKGBUILDDIR>>/src/core/n2dVersion.cxx:21:0: > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/Nifti2DicomConfig.h:31:10: fatal error: > gdcmVersion.h: No such file or directory > #include <gdcmVersion.h> > ^~~~~~~~~~~~~~~ > compilation terminated. > src/core/CMakeFiles/nifti2dicom_core.dir/build.make:65: recipe for target > 'src/core/CMakeFiles/nifti2dicom_core.dir/n2dVersion.cxx.o' failed > make[3]: *** [src/core/CMakeFiles/nifti2dicom_core.dir/n2dVersion.cxx.o] > Error 1 The full build log is available from: http://aws-logs.debian.net/2017/08/05/nifti2dicom_0.4.11-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
