Bug#866354: marked as done (armel: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6)
Your message dated Sat, 16 Mar 2019 11:19:16 + with message-id and subject line Bug#866354: fixed in gcc-8 8.3.0-3 has caused the Debian Bug report #866354, regarding armel: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 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.) -- 866354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libstdc++6 Version: 7.1.0-7 Severity: serious Control: affects -1 src:mesa mesa FTBFS on armel due to: https://buildd.debian.org/status/fetch.php?pkg=mesa=armel=17.1.3-2=1498610882=0 ... llvm-config-4.0: relocation error: /usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 with link time reference llvm-config-4.0: relocation error: /usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 with link time reference llvm-config-4.0: relocation error: /usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 with link time reference llvm-config-4.0: relocation error: /usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 with link time reference ... My first guess would be that the #727621 fix might be missing or broken in GCC 7. --- End Message --- --- Begin Message --- Source: gcc-8 Source-Version: 8.3.0-3 We believe that the bug you reported is fixed in the latest version of gcc-8, 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 866...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-8 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: Sat, 16 Mar 2019 11:41:45 +0100 Source: gcc-8 Architecture: source Version: 8.3.0-3 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 866354 Changes: gcc-8 (8.3.0-3) unstable; urgency=medium . * Update to SVN 20190316 (r269720) from the gcc-8-branch. - Fix PR tree-optimization/89505, PR target/89517 (AArch64), PR bootstrap/89539, PR debug/88878, PR debug/89514, PR tree-optimization/89536, PR target/88100 (PPC), PR target/89397 (x86), PR target/89361 (S390), PR c++/89212, PR fortran/89077, PR fortran/77583, PR fortran/89174, PR fortran/87689, PR fortran/84387, PR fortran/89516, PR fortran/89492, PR fortran/89266, PR fortran/88326, PR libfortran/89020, PR target/88530 (AArch64), PR target/88530 (AArch64), PR ipa/88235, PR c++/88820, PR c++/88869, PR c++/88419, PR c++/88690, PR c++/87921, PR c++/89381, PR c++/89576, PR c++/89422, PR c++/87513, PR c++/88183, PR c++/89585, PR fortran/71544, PR fortran/87734, PR fortran/71203, PR fortran/72714, PR middle-end/89572, PR target/85860, PR middle-end/89677, PR middle-end/89497, PR tree-optimization/89296, PR tree-optimization/89664, PR rtl-optimization/89588, PR lto/88147, PR target/86952 (x86), PR lto/88147, PR fortran/87673, PR c++/89383, PR lto/87525, PR other/89712, PR testsuite/85368. * Backport libgo patches for the Hurd from the trunk (Svante Signell). * Add some more breaks to libstdc++6. Closes: #866354. Checksums-Sha1: 289eef74f89e06705557422c66f9d43dfe25a251 32433 gcc-8_8.3.0-3.dsc b3430f476c16fc8607c508da13121a091fc9ef57 684830 gcc-8_8.3.0-3.diff.gz bcc2d9f108f3c764da3fe17695af8c690b0dabb6 10310 gcc-8_8.3.0-3_source.buildinfo Checksums-Sha256: 0c737e3b3d6169a43177b10568a035990d555b59312408710c40a7fe1b576085 32433 gcc-8_8.3.0-3.dsc c1241b56a675f0112ae4d8db87abdef7c5707fe1048ca11849d8e886aec91e80 684830 gcc-8_8.3.0-3.diff.gz 688bb43186adc2da03eb1b7040588cdbb3594e1b78762fee616f7a76a5a609a7 10310 gcc-8_8.3.0-3_source.buildinfo Files:
Bug#866354: marked as done (armel: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6)
Your message dated Sun, 27 Aug 2017 03:01:17 + with message-idand subject line Bug#866354: fixed in llvm-toolchain-4.0 1:4.0.1-2 has caused the Debian Bug report #866354, regarding armel: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 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.) -- 866354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libstdc++6 Version: 7.1.0-7 Severity: serious Control: affects -1 src:mesa mesa FTBFS on armel due to: https://buildd.debian.org/status/fetch.php?pkg=mesa=armel=17.1.3-2=1498610882=0 ... llvm-config-4.0: relocation error: /usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 with link time reference llvm-config-4.0: relocation error: /usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 with link time reference llvm-config-4.0: relocation error: /usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 with link time reference llvm-config-4.0: relocation error: /usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 with link time reference ... My first guess would be that the #727621 fix might be missing or broken in GCC 7. --- End Message --- --- Begin Message --- Source: llvm-toolchain-4.0 Source-Version: 1:4.0.1-2 We believe that the bug you reported is fixed in the latest version of llvm-toolchain-4.0, 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 866...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated llvm-toolchain-4.0 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: Sat, 26 Aug 2017 17:36:26 +0200 Source: llvm-toolchain-4.0 Binary: clang-4.0 clang-format-4.0 clang-tidy-4.0 clang-4.0-doc libclang1-4.0 libclang1-4.0-dbg libclang-4.0-dev libclang-common-4.0-dev libfuzzer-4.0-dev python-clang-4.0 clang-4.0-examples libllvm4.0 libllvm4.0-dbg llvm-4.0 llvm-4.0-runtime llvm-4.0-dev llvm-4.0-tools libllvm-4.0-ocaml-dev llvm-4.0-doc llvm-4.0-examples lld-4.0 liblld-4.0 liblld-4.0-dbg liblld-4.0-dev lldb-4.0 liblldb-4.0 liblldb-4.0-dbg python-lldb-4.0 liblldb-4.0-dev Architecture: source amd64 all Version: 1:4.0.1-2 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Description: clang-4.0 - C, C++ and Objective-C compiler (LLVM based) clang-4.0-doc - C, C++ and Objective-C compiler (LLVM based) - Documentation clang-4.0-examples - Clang examples clang-format-4.0 - Tool to format C/C++/Obj-C code clang-tidy-4.0 - clang-based C++ linter tool libclang-4.0-dev - clang library - Development package libclang-common-4.0-dev - clang library - Common development package libclang1-4.0 - C interface to the clang library libclang1-4.0-dbg - clang library libfuzzer-4.0-dev - Library for coverage-guided fuzz testing liblld-4.0 - LLVM-based linker, library liblld-4.0-dbg - LLVM-based linker, debugging libraries liblld-4.0-dev - LLVM-based linker, header files liblldb-4.0 - Next generation, high-performance debugger, library liblldb-4.0-dbg - Next generation, high-performance debugger, debugging libraries liblldb-4.0-dev - Next generation, high-performance debugger, header files libllvm-4.0-ocaml-dev - Modular compiler and toolchain technologies, OCaml bindings libllvm4.0 - Modular compiler and toolchain technologies, runtime library libllvm4.0-dbg - Modular compiler and toolchain technologies, debugging libraries lld-4.0- LLVM-based linker lldb-4.0 - Next generation, high-performance debugger llvm-4.0 - Modular