public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nightstrike at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/99794] libphobos: Support building on *-*mingw* Date: Thu, 12 Jan 2023 17:25:57 +0000 [thread overview] Message-ID: <bug-99794-4-ecc9OSYgIf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99794-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99794 nightstrike <nightstrike at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nightstrike at gmail dot com --- Comment #2 from nightstrike <nightstrike at gmail dot com> --- Hoping this can be backported to 11 so that we can easily bootstrap later versions. Meanwhile, will this also fix the build errors on cygwin, or if is specific to mingw?
next prev parent reply other threads:[~2023-01-12 17:25 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-26 15:49 [Bug d/99794] New: " ibuclaw at gdcproject dot org 2021-04-19 17:28 ` [Bug d/99794] " cvs-commit at gcc dot gnu.org 2023-01-12 17:25 ` nightstrike at gmail dot com [this message] 2023-01-12 19:37 ` nightstrike at gmail dot com
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-99794-4-ecc9OSYgIf@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).