public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rust/113056] [14 regression] Build failure in libgrust Date: Mon, 18 Dec 2023 06:20:05 +0000 [thread overview] Message-ID: <bug-113056-4-J0zQwq9QMo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113056-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113056 --- Comment #5 from Sam James <sjames at gcc dot gnu.org> --- ftr (given I only gave a packaged build log) repro'd with ./configure --prefix=/tmp/gcc --enable-languages=c,c++,rust --enable-multilib --with-multilib-list=m32,m64 --with-checking=yes,extra,rtl --disable-analyzer --disable-cet --disable-default-pie --disable-default-ssp --disable-gcov --disable-libada --disable-libatomic --disable-libgomp --disable-libitm --disable-libquadmath --disable-libsanitizer --disable-libssp --disable-libstdcxx-pch --disable-libvtv --disable-lto --disable-nls --disable-objc-gc --disable-systemtap --disable-werror && make
next prev parent reply other threads:[~2023-12-18 6:20 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-18 5:36 [Bug rust/113056] New: " sjames at gcc dot gnu.org 2023-12-18 5:37 ` [Bug rust/113056] " sjames at gcc dot gnu.org 2023-12-18 5:38 ` sjames at gcc dot gnu.org 2023-12-18 5:39 ` pinskia at gcc dot gnu.org 2023-12-18 5:43 ` pinskia at gcc dot gnu.org 2023-12-18 6:20 ` sjames at gcc dot gnu.org [this message] 2023-12-18 7:48 ` pinskia at gcc dot gnu.org 2023-12-18 7:50 ` pinskia at gcc dot gnu.org 2023-12-18 7:52 ` sjames at gcc dot gnu.org 2023-12-18 7:55 ` pinskia at gcc dot gnu.org 2023-12-18 8:24 ` rguenth at gcc dot gnu.org 2023-12-18 13:08 ` sjames at gcc dot gnu.org 2023-12-18 15:26 ` tschwinge at gcc dot gnu.org 2023-12-18 17:02 ` tschwinge at gcc dot gnu.org 2024-01-08 11:02 ` cvs-commit at gcc dot gnu.org 2024-01-08 11:08 ` tschwinge at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-113056-4-J0zQwq9QMo@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).