Your message dated Sun, 06 Aug 2017 11:00:30 +0200
with message-id <1502010030.6022.2.ca...@gmail.com>
and subject line Re: elastix: ftbfs with GCC-7
has caused the Debian Bug report #853386,
regarding nifti2dicom: ftbfs with GCC-7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
853386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nifti2dicom
Version: 0.4.11-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/nifti2dicom_0.4.11-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.
To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html
[...]
"/usr/bin/vtk"
but this file does not exist. Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
"/usr/lib/cmake/vtk-6.3/VTKTargets.cmake"
but not all the files it references.
-- Configuring done
-- Generating done
-- Build files have been written to: /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu
/usr/bin/make -C obj-x86_64-linux-gnu
make[1]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
/usr/bin/cmake -H/<<PKGBUILDDIR>> -B/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/CMakeFiles
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
/usr/bin/make -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
/usr/bin/make -f src/core/CMakeFiles/nifti2dicom_core.dir/build.make
src/core/CMakeFiles/nifti2dicom_core.dir/depend
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends
"Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/src/core
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/core
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/core/CMakeFiles/nifti2dicom_core.dir/DependInfo.cmake
--color=
Scanning dependencies of target nifti2dicom_core
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
/usr/bin/make -f src/core/CMakeFiles/nifti2dicom_core.dir/build.make
src/core/CMakeFiles/nifti2dicom_core.dir/build
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
[ 2%] Building CXX object
src/core/CMakeFiles/nifti2dicom_core.dir/n2dVersion.cxx.o
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/<<PKGBUI
LDDIR>>/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"
^~~~~
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
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:111: recipe for target
'src/core/CMakeFiles/nifti2dicom_core.dir/all' failed
make[2]: *** [src/core/CMakeFiles/nifti2dicom_core.dir/all] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
Makefile:152: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
/usr/share/cdbs/1/class/makefile.mk:77: recipe for target
'debian/stamp-makefile-build' failed
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Version: 4.12.0-dfsg1-1
closing this manually because the upload was already in the works when
these bugs were filed.
Best,
Gert
--- End Message ---
