Your message dated Fri, 24 Feb 2017 10:40:31 +0100
with message-id <[email protected]>
and subject line Re: Bug#853500: libosmium: ftbfs with GCC-7
has caused the Debian Bug report #853500,
regarding libosmium: 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.)
--
853500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853500
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:libosmium
Version: 2.11.0-1
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/libosmium_2.11.0-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
[...]
66: Test timeout computed to be: 9.99988e+06
66: Pass 1...
66: Pass 1 done
66: Pass 2...
66: 8.8721, 53.0966 post_office
66: Pass 2 done
66/68 Test #66: examples_amenity_list .................... Passed 0.01 sec
test 67
Start 67: examples_pub_names
67: Test command: /<<PKGBUILDDIR>>/build/examples/osmium_pub_names
"/<<PKGBUILDDIR>>/test/examples/t/pub_names/pubs.osm"
67: Test timeout computed to be: 9.99988e+06
67: Im Holze
67/68 Test #67: examples_pub_names ....................... Passed 0.00 sec
test 68
Start 68: examples_road_length
68: Test command: /<<PKGBUILDDIR>>/build/examples/osmium_road_length
"/<<PKGBUILDDIR>>/test/examples/t/road_length/road.osm"
68: Test timeout computed to be: 9.99988e+06
68: Length: 0.405759 km
68/68 Test #68: examples_road_length ..................... Passed 0.00 sec
97% tests passed, 2 tests failed out of 68
Label Time Summary:
area = 0.01 sec (2 tests)
builder = 0.01 sec (2 tests)
fast = 0.64 sec (65 tests)
geom = 0.24 sec (13 tests)
index = 0.18 sec (5 tests)
io = 0.12 sec (13 tests)
memory = 0.01 sec (4 tests)
osm = 0.04 sec (13 tests)
tags = 0.01 sec (3 tests)
thread = 0.01 sec (1 test)
unit = 0.64 sec (65 tests)
util = 0.02 sec (9 tests)
Total Test time (real) = 0.68 sec
The following tests FAILED:
25 - geom_test_factory_with_projection (Failed)
34 - geom_test_wkt (Failed)
Errors while running CTest
debian/rules:27: recipe for target 'override_dh_auto_test-arch' failed
make[1]: *** [override_dh_auto_test-arch] Error 8
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
debian/rules:11: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
On 02/02/2017 07:28 PM, Sebastiaan Couwenberg wrote:
> On 01/31/2017 10:33 AM, Matthias Klose wrote:
>> 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/libosmium_2.11.0-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++
>
> I cannot reproduce the issue with g++-7 from experimental, and neither
> can upstream.
>
> I'm going to close this bugreport if your follow-up test doesn't happen
> soon.
Closing this issue as it cannot be reproduced.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
_______________________________________________
Pkg-grass-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
