public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/67112] New: [MinGW64] build failure due to name conflict with system headers
@ 2015-08-04 10:39 sliwa at ifpan dot edu.pl
  2015-08-04 11:48 ` [Bug libstdc++/67112] " redi at gcc dot gnu.org
  2021-08-12 17:26 ` redi at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: sliwa at ifpan dot edu.pl @ 2015-08-04 10:39 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67112

            Bug ID: 67112
           Summary: [MinGW64] build failure due to name conflict with
                    system headers
           Product: gcc
           Version: 5.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: sliwa at ifpan dot edu.pl
  Target Milestone: ---

Created attachment 36118
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36118&action=edit
proposed path

libstdc++ fails to build on MinGW64 due to a name conflict:

* the macro "C" is #defined to the character type for which classes templates
are being instantiated

* the name "C" is used as the name of a field in a struct in winnt.h (a MinGW
system header file)

The attached patch changes the name of the parameter macro to "CHARC".


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug libstdc++/67112] [MinGW64] build failure due to name conflict with system headers
  2015-08-04 10:39 [Bug libstdc++/67112] New: [MinGW64] build failure due to name conflict with system headers sliwa at ifpan dot edu.pl
@ 2015-08-04 11:48 ` redi at gcc dot gnu.org
  2021-08-12 17:26 ` redi at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2015-08-04 11:48 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67112

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-08-04
     Ever confirmed|0                           |1


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug libstdc++/67112] [MinGW64] build failure due to name conflict with system headers
  2015-08-04 10:39 [Bug libstdc++/67112] New: [MinGW64] build failure due to name conflict with system headers sliwa at ifpan dot edu.pl
  2015-08-04 11:48 ` [Bug libstdc++/67112] " redi at gcc dot gnu.org
@ 2021-08-12 17:26 ` redi at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2021-08-12 17:26 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67112

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WORKSFORME
             Status|NEW                         |RESOLVED

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Apparently nobody in the mingw-w64 community has seen this or can reproduce it,
so I'm closing as WORKSFORME.

If you are still seeing this with current GCC releases, please reopen and
provide more details.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-08-12 17:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-08-04 10:39 [Bug libstdc++/67112] New: [MinGW64] build failure due to name conflict with system headers sliwa at ifpan dot edu.pl
2015-08-04 11:48 ` [Bug libstdc++/67112] " redi at gcc dot gnu.org
2021-08-12 17:26 ` redi at gcc dot gnu.org

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).