public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/97484] typedef conflict for "byte" in GCC11 for MinGW-w64 Date: Mon, 19 Oct 2020 08:26:42 +0000 [thread overview] Message-ID: <bug-97484-4-XJgtCIb4E4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97484-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97484 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Does Ninja use using namespace std; before including standard headers, or does some mingw header use that?
next prev parent reply other threads:[~2020-10-19 8:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-19 6:27 [Bug c++/97484] New: " brechtsanders at users dot sourceforge.net 2020-10-19 8:04 ` [Bug libstdc++/97484] " rguenth at gcc dot gnu.org 2020-10-19 8:26 ` jakub at gcc dot gnu.org [this message] 2020-10-19 9:39 ` brechtsanders at users dot sourceforge.net 2020-10-19 9:45 ` jakub at gcc dot gnu.org 2020-10-19 10:09 ` brechtsanders at users dot sourceforge.net 2020-10-19 10:20 ` jakub at gcc dot gnu.org 2023-03-14 21:13 ` Abderraouf.bousri at g dot enp.edu.dz
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-97484-4-XJgtCIb4E4@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).