Your message dated Sat, 25 Mar 2017 11:42:46 +0100
with message-id <[email protected]>
and subject line mia: ftbfs with GCC-7
has caused the Debian Bug report #853549,
regarding mia: 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 [email protected]
immediately.)
--
853549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853549
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:mia
Version: 2.4.3-5
Severity: normal
Tags: sid buster
User: [email protected]
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/mia_2.4.3-5_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/ld:
CMakeFiles/test-1d-splinekernel-bspline.dir/test_bspline.cc.o(.text+0x436):
unresolvable R_X86_64_TPOFF32 relocation against symbol
`_ZN3mia7vstream15m_message_levelE'
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
mia/core/splinekernel/CMakeFiles/test-1d-splinekernel-bspline.dir/build.make:104:
recipe for target 'mia/core/splinekernel/test-1d-splinekernel-bspline' failed
make[4]: *** [mia/core/splinekernel/test-1d-splinekernel-bspline] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:5904: recipe for target
'mia/core/splinekernel/CMakeFiles/test-1d-splinekernel-bspline.dir/all' failed
make[3]: ***
[mia/core/splinekernel/CMakeFiles/test-1d-splinekernel-bspline.dir/all] Error 2
[ 20%] Linking CXX executable test-core
cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/mia/core && /usr/bin/cmake -E
cmake_link_script CMakeFiles/test-core.dir/link.txt --verbose=1
/usr/bin/c++ -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -std=c++11 -fvisibility=hidden -Wl,-z,relro -Wl,-z,now
-Wl,--as-needed -fvisibility=hidden
CMakeFiles/test-core.dir/test_core_combined.cc.o -o test-core
-Wl,-rpath,/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/mia/core -rdynamic
libmiacore-2.4.so.2.0.1 -lgsl -lgslcblas -lm -lboost_filesystem -lboost_system
-lpthread -ldl -lboost_unit_test_framework -lfftw3f -lxml++-2.6 -lxml2
-lglibmm-2.4 -lgobject-2.0 -lglib-2.0 -lsigc-2.0 -litpp
/usr/bin/ld: CMakeFiles/test-core.dir/test_core_combined.cc.o(.text+0xd22):
unresolvable R_X86_64_TPOFF32 relocation against symbol
`_ZN3mia7vstream15m_message_levelE'
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
mia/core/CMakeFiles/test-core.dir/build.make:102: recipe for target
'mia/core/test-core' failed
make[4]: *** [mia/core/test-core] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:2872: recipe for target
'mia/core/CMakeFiles/test-core.dir/all' failed
make[3]: *** [mia/core/CMakeFiles/test-core.dir/all] Error 2
make[4]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
[ 20%] Built target 3dimage-cost-ssd-automask-common
make[4]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
[ 20%] Built target 3dimage-maskedcost-mi-common
make[4]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
[ 20%] Built target 2dimage-cost-lncc-common
make[4]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
[ 20%] Built target 3dimage-cost-lncc-common
make[4]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
[ 20%] Built target 2dimage-cost-ncc-common
make[4]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
[ 20%] Built target 2dimage-maskedcost-lncc-common
make[4]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
[ 20%] Built target 2dimage-maskedcost-ncc-common
make[4]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
[ 20%] Built target 3dimage-cost-ncc-common
make[4]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
[ 20%] Built target 3dimage-maskedcost-ncc-common
make[4]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
[ 20%] Built target 3dimage-maskedcost-lncc-common
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
Makefile:141: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
dh_auto_build: make -j64 returned exit code 2
debian/rules:44: recipe for target 'override_dh_auto_build-arch' failed
make[1]: *** [override_dh_auto_build-arch] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
debian/rules:22: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Package: src:mia
Version: 2.4.3-5
I'm closing this because I can't reproduce the bug with the latest
version of g++: 7-20170316-1.
I guess it was actually a problem with gcc itself that is now fixed.
Best,
Gert
--- End Message ---
