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/113553] rust fails to build on sparc64-linux-gnu Date: Thu, 01 Feb 2024 17:39:02 +0000 [thread overview] Message-ID: <bug-113553-4-JA2YnvohaE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113553-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113553 Sam James <sjames at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=112836 --- Comment #4 from Sam James <sjames at gcc dot gnu.org> --- Adding PR112836 to See Also because (part of this) involves posix_spawn on sparc. Wonder if Rainer's issue - which I've hit too - is the same as the one I'm seeing on glibc too.
next prev parent reply other threads:[~2024-02-01 17:39 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-23 8:15 [Bug rust/113553] New: rust fails to build on spar64-linux-gnu doko at gcc dot gnu.org 2024-01-24 14:33 ` [Bug rust/113553] rust fails to build on sparc64-linux-gnu ro at gcc dot gnu.org 2024-02-01 6:26 ` pinskia at gcc dot gnu.org 2024-02-01 11:40 ` doko at gcc dot gnu.org 2024-02-01 17:39 ` sjames at gcc dot gnu.org [this message] 2024-02-01 19:10 ` glaubitz at physik dot fu-berlin.de 2024-02-01 19:16 ` pinskia at gcc dot gnu.org 2024-02-01 19:18 ` sjames at gcc dot gnu.org 2024-02-01 19:54 ` glaubitz at physik dot fu-berlin.de 2024-02-01 20:03 ` pinskia at gcc dot gnu.org 2024-02-01 20:09 ` glaubitz at physik dot fu-berlin.de 2024-02-01 20:16 ` pinskia at gcc dot gnu.org 2024-02-02 8:39 ` bruno at clisp dot org 2024-02-02 8:43 ` pinskia at gcc dot gnu.org 2024-02-12 23:40 ` glaubitz at physik dot fu-berlin.de
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-113553-4-JA2YnvohaE@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).