Your message dated Wed, 29 Jun 2016 18:21:41 +0000 with message-id <e1bik7j-0002hn...@franck.debian.org> and subject line Bug#812289: fixed in google-mock 1.7.0-18092013-2 has caused the Debian Bug report #812289, regarding google-mock: FTBFS with GCC 6: test suite segfault 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.) -- 812289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: google-mock Version: 1.7.0-18092013-1 Severity: normal User: debian-...@lists.debian.org Usertags: ftbfs-gcc-6 gcc-6-unknown This package fails to build with GCC 6. GCC 6 has not been released yet, but it's expected that GCC 6 will become the default compiler for stretch. Unfortunately, it's not clear from the log why the build failed. It's possible there's a bug in this package or in GCC. It's also possible I reported a non-issue, although I tried to avoid that. I apologize in advance if this is the case. If you have some time to look into this issue, that'd be great. If not, I can re-test the package with GCC 6 in a few weeks time. You can find a snapshot of GCC 6 in experimental. To build with GCC 6, you can set CC=gcc-6 CXX=g++-6 explicitly. You may be able to find out more about this issue at https://gcc.gnu.org/gcc-6/changes.html > sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux ... > [ OK ] ExpectCallSyntaxTest.CompilesWithMethodNameExpandedFromMacro (0 > ms) > [ RUN ] ExpectCallSyntaxTest.WorksWithMethodNameExpandedFromMacro > [ OK ] ExpectCallSyntaxTest.WorksWithMethodNameExpandedFromMacro (0 ms) > [ RUN ] ExpectCallSyntaxTest.EvaluatesFirstArgumentOnce > /bin/bash: line 5: 37395 Segmentation fault ${dir}$tst > FAIL: test/gmock-spec-builders_test > Running main() from gmock_main.cc > [==========] Running 92 tests from 2 test cases. > [----------] Global test environment set-up. > [----------] 46 tests from LinkTest2 > [ RUN ] LinkTest2.TestReturnVoid > /bin/bash: line 5: 38660 Segmentation fault ${dir}$tst > FAIL: test/gmock_link_test > ============================================ > 2 of 2 tests failed > Please report to googlem...@googlegroups.com > ============================================ > Makefile:882: recipe for target 'check-TESTS' failed -- Martin Michlmayr Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---Source: google-mock Source-Version: 1.7.0-18092013-2 We believe that the bug you reported is fixed in the latest version of google-mock, 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 812...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fredrik Hallenberg <hal...@debian.org> (supplier of updated google-mock 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 ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Wed, 29 Jun 2016 17:32:19 +0200 Source: google-mock Binary: google-mock Architecture: source amd64 Version: 1.7.0-18092013-2 Distribution: unstable Urgency: medium Maintainer: Fredrik Hallenberg <hal...@debian.org> Changed-By: Fredrik Hallenberg <hal...@debian.org> Description: google-mock - Google's framework for writing and using C++ mock classes Closes: 812289 Changes: google-mock (1.7.0-18092013-2) unstable; urgency=medium . * Use -fno-delete-null-pointer-checks to work with gcc 6. (closes: #812289). Just a workaround, hopefully a proper fix is done in a future upstream release. Checksums-Sha1: 4272a8e08c29ef4c00c907c75a9022408c867d8b 1851 google-mock_1.7.0-18092013-2.dsc fecc4854563b686dd571f2099f62053dd9a1e52d 5412 google-mock_1.7.0-18092013-2.debian.tar.xz e0f459efccecbfe1fe010282dbd1b40274fa0c76 117962 google-mock_1.7.0-18092013-2_amd64.deb Checksums-Sha256: 77ff7b7bcd9a40c728e0edec4042c902ed0ffef24dfd7b3335dbbecffc677196 1851 google-mock_1.7.0-18092013-2.dsc 0687e89f4fabcc2c7bf9228d65431f288afc079a33c12494ea89fa56b507f7db 5412 google-mock_1.7.0-18092013-2.debian.tar.xz 9eeb98f138306c77b79699e5a51415bba8aa9555a022bc25ba921d7ca56574c7 117962 google-mock_1.7.0-18092013-2_amd64.deb Files: c3f17e8c3c7d0feee90be8c847445920 1851 devel optional google-mock_1.7.0-18092013-2.dsc 0047e1ba3da755ffdc5035ad607d11bc 5412 devel optional google-mock_1.7.0-18092013-2.debian.tar.xz 30d77c66c8423665cf3d0cc2a6c90b62 117962 devel optional google-mock_1.7.0-18092013-2_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIVAwUBV3QIpeM325NCbkFUAQj/nBAAgucY2Tmi14O1Whd6oBcHPoK8e/5VDrcR MJVKlbjuOZZtsjkT3nlrkj7DZiI7ZUdtU8dGh72qXP/CU7HhvQv7PhdIT5VvHv8U 8VaNsPRdtsZtwdFjvFO1eVRPHP+KkZvpbVgW9vAYApf/Jst4JjNorN4ZkEygCDcD ryv3LiHoVjl6TrGHAW09/SMDGDPJZL3+KspZlQB1jr428Dwn31rqxkIq7CJTf3jP 4+eOlyCENITcZPGc04eIsiHH6AHkeBXeLyJHCxq7UFR7kNr4w8zQBr/0//CxP1he zjouxdsYxTdgADdZum+7/A3YZQmu+4gQ9LyQkz+ZujqBU9ECB2UbaSRV7ZwFi+MK 9G6bO80W4rzIV/lllOJQ+zVd5fwfNon+QdvGQWwp8vXTlC3aZ1d8cFChT94R6GV5 v1EH/XabU26fvZrzql1JNnAraodRChmTcFtlcyV2zECkxZUod2oyTYX13XXkTzU0 C2C6a49v18mvQapgrYe6JTe8j7tBAoPnfOfeSNgTTpL5q4MUhmO2LZXQ0CvlUhvw SISp+jVtD9/hRiID1WSrGhrm9xcGwDMS956Hy/2ukzAGAEMu55Z/N+qUEe5i/2ts /suDJfdrAnogxX3Bjc+oLSus2cripXpct9V5osG913iW7Ig7KUI+nB0HZHVDTiJP Rf6fMxaSmUQ= =slaf -----END PGP SIGNATURE-----
--- End Message ---
