Your message dated Mon, 06 Jul 2020 16:19:05 +0000
with message-id <[email protected]>
and subject line Bug#957297: fixed in google-perftools 2.8-1
has caused the Debian Bug report #957297,
regarding google-perftools: ftbfs with GCC-10
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.)


-- 
957297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957297
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:google-perftools
Version: 2.7-1
Severity: normal
Tags: sid bullseye
User: [email protected]
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/google-perftools_2.7-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html

[...]
PASS: tcmalloc_minimal_debug_unittest
PASS: malloc_extension_debug_test
PASS: memalign_debug_unittest
PASS: realloc_debug_unittest
rm -f debugallocation_test.sh
cp -p ./src/tests/debugallocation_test.sh debugallocation_test.sh
FAIL: debugallocation_test.sh
rm -f tcmalloc_unittest.sh
cp -p ./src/tests/tcmalloc_unittest.sh tcmalloc_unittest.sh
PASS: tcmalloc_unittest.sh
PASS: tcmalloc_both_unittest
PASS: tcmalloc_large_unittest
PASS: tcmalloc_large_heap_fragmentation_unittest
PASS: raw_printer_test
PASS: sampler_test
rm -f sampling_test.sh
cp -p ./src/tests/sampling_test.sh sampling_test.sh
PASS: sampling_test.sh
rm -f heap-profiler_unittest.sh
cp -p ./src/tests/heap-profiler_unittest.sh heap-profiler_unittest.sh
PASS: heap-profiler_unittest.sh
PASS: simple_compat_test
rm -f heap-checker_unittest.sh
cp -p ./src/tests/heap-checker_unittest.sh heap-checker_unittest.sh
PASS: heap-checker_unittest.sh
rm -f heap-checker-death_unittest.sh
cp -p ./src/tests/heap-checker-death_unittest.sh heap-checker-death_unittest.sh
PASS: heap-checker-death_unittest.sh
PASS: tcmalloc_debug_unittest
PASS: sampler_debug_test
rm -f sampling_debug_test.sh
cp -p ./src/tests/sampling_test.sh sampling_debug_test.sh
PASS: sampling_debug_test.sh
rm -f heap-profiler_debug_unittest.sh
cp -p ./src/tests/heap-profiler_unittest.sh heap-profiler_debug_unittest.sh
PASS: heap-profiler_debug_unittest.sh
rm -f heap-checker_debug_unittest.sh
cp -p ./src/tests/heap-checker_unittest.sh heap-checker_debug_unittest.sh
PASS: heap-checker_debug_unittest.sh
PASS: getpc_test
PASS: profiledata_unittest
PASS: profile_handler_unittest
rm -f profiler_unittest.sh
cp -p ./src/tests/profiler_unittest.sh profiler_unittest.sh
PASS: profiler_unittest.sh
PASS: tcmalloc_and_profiler_unittest
============================================================================
Testsuite summary for gperftools 2.7
============================================================================
# TOTAL: 48
# PASS:  46
# SKIP:  0
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0
============================================================================
See ./test-suite.log
Please report to [email protected]
============================================================================
make[4]: *** [Makefile:6511: test-suite.log] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>'
make[3]: *** [Makefile:6619: check-TESTS] Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>'
make[2]: *** [Makefile:7164: check-am] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [debian/rules:34: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: google-perftools
Source-Version: 2.8-1
Done: Laszlo Boszormenyi (GCS) <[email protected]>

We believe that the bug you reported is fixed in the latest version of
google-perftools, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS) <[email protected]> (supplier of updated 
google-perftools package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 06 Jul 2020 17:03:50 +0200
Source: google-perftools
Architecture: source
Version: 2.8-1
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) <[email protected]>
Changed-By: Laszlo Boszormenyi (GCS) <[email protected]>
Closes: 739571 957297
Changes:
 google-perftools (2.8-1) unstable; urgency=medium
 .
   * New major upstream release:
     - fixes FTBFS with GCC 10 (closes: #957297).
   * Add suggests of libgoogle-perftools-dev to google-perftools
     (closes: #739571).
Checksums-Sha1:
 ec4b364838231844a79b5736cdb5a0feac953aa9 2203 google-perftools_2.8-1.dsc
 6c68b8b57202323bd0c112fb5608e7ea928efb36 928379 
google-perftools_2.8.orig.tar.gz
 71f94eb46d3270aaf3891ffb6843939237461a24 6804 
google-perftools_2.8-1.debian.tar.xz
Checksums-Sha256:
 4d349d7874df32b7e922c5d43b60a694328985ed034d1a67fabfe281e7cc5f85 2203 
google-perftools_2.8-1.dsc
 b09193adedcc679df2387042324d0d54b93d35d062ea9bff0340f342a709e860 928379 
google-perftools_2.8.orig.tar.gz
 a18fd4f4dcfb705b651539ec93b49aecdc8e9b92c3f7a1ad7c7a743b3b988c5a 6804 
google-perftools_2.8-1.debian.tar.xz
Files:
 45bf9eea71ef33cd914e27580ce6a82f 2203 libs optional google-perftools_2.8-1.dsc
 8bc8278ff3367fbb472a1dfc6d1e0833 928379 libs optional 
google-perftools_2.8.orig.tar.gz
 2a5312cf1801a17b3466956b52d7714c 6804 libs optional 
google-perftools_2.8-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl8DSM0ACgkQ3OMQ54ZM
yL/rlw/+I8oMXWEV6JA71ninstl1gbsO6SVw1wJn5/NMF6P9w2B/VDTpV++U1Yeg
kybQ26DjMnd5aFfpigIm7qSjuYqPuUu3MRkUnn4gJCmk1GSLpZhwOj3WXLGdJyuk
X56fGSXqxCBsp3sSP2MrzTEMYbzWGeoq6OuzwHV5zN/fVnBMc/J4Rqx1uCIXK0+g
oDbsNu91mQQzLYFMXYczvDQo5FEEluGQkpG6w5IlFmgLpYFVAdRmt7/Y8dGmTBte
IrRkwOmHMjILMnAxSI23ZeBlrFC9nUdbazCbPlMFXkmgmC1gy7ZW6HByRd5vDlq6
QkwLE4qMoXi06p4mP6ehrZd5+F719ky2d5vM7zdWsuCX+wtZw1eBzoA/1QXRJDuw
UVu+eoSYKRhWIDmh4ZSUKG1WC6ihUCBBbFDNvSEi5K5cKkVgGm3hogGBPGBkO2q9
ehRQqvp+D7jNBgKdzGkuqn7Uai2PhLbT0ZSu665zubxOE6jx0z4XjfgSeFfVZmRN
ZhsGMawEhWA0yerZahvCXhsGKYZT90EOltlIU6C2sUOfbbKBt6OCSYzBN7TTg85u
8OsGlkpSYmQUxG5q9FNBEdbhKqfxtEveBG7losbUan9EMIoauPCUeHtwY9A6qVny
eOic56heMv4oUsqgcAoiJoLB1FbvrutbHeZsoTtLsTx907HqAdU=
=c10g
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to