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 other/38294] New: Enable multilib support for mingw Date: Thu, 27 Nov 2008 17:42:00 -0000 [thread overview] Message-ID: <bug-38294-14772@http.gcc.gnu.org/bugzilla/> (raw) Now that we have a viable header set and libraries for x86_64-pc-mingw32, we are able to support multilib. This needs to be enabled. -- Summary: Enable multilib support for mingw Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: other AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: nightstrike at gmail dot com GCC target triplet: x86_64-*-mingw32 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38294
next reply other threads:[~2008-11-27 17:42 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-11-27 17:42 nightstrike at gmail dot com [this message] 2008-11-27 17:42 ` [Bug other/38294] " nightstrike at gmail dot com 2008-11-27 17:45 ` nightstrike at gmail dot com 2008-12-08 7:50 ` [Bug target/38294] " nightstrike at gmail dot com 2008-12-08 20:18 ` ktietz at gcc dot gnu dot org 2008-12-13 21:20 ` nightstrike at gmail dot com 2008-12-13 21:48 ` ktietz at gcc dot gnu dot org 2008-12-13 22:01 ` nightstrike at gmail dot com 2008-12-13 23:02 ` nightstrike at gmail dot com 2008-12-14 0:12 ` nightstrike at gmail dot com 2008-12-14 5:56 ` dannysmith at users dot sourceforge dot net 2008-12-14 7:51 ` ktietz at gcc dot gnu dot org 2009-02-06 4:21 ` nightstrike at gmail dot com 2009-08-31 19:49 ` ktietz at gcc dot gnu dot org 2009-08-31 19:52 ` ktietz at gcc dot gnu dot 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-38294-14772@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).