public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andris.pavenis at iki dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/64553] Missing '# ifdef _GLIBCXX_USE_WCHAR_T' in src/c++11/cxx11-shim_facet.cc
Date: Fri, 09 Jan 2015 19:30:00 -0000	[thread overview]
Message-ID: <bug-64553-4-DJ1fVUsieW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64553-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Andris Pavenis <andris.pavenis at iki dot fi> ---
Created attachment 34415
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34415&action=edit
A patch

After included patch for cxx11-shim_facets.cc native bootstrap succeeded for
DJGPP (C, C++, Fortran, Objc, ObjC++). There were however other DJGPP related
changes


  reply	other threads:[~2015-01-09 19:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 19:14 [Bug libstdc++/64553] New: " andris.pavenis at iki dot fi
2015-01-09 19:30 ` andris.pavenis at iki dot fi [this message]
2015-01-10 15:13 ` [Bug libstdc++/64553] [5 Regression] " redi at gcc dot gnu.org
2015-01-12 21:46 ` redi at gcc dot gnu.org
2015-01-12 21:48 ` redi at gcc dot gnu.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-64553-4-DJ1fVUsieW@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: link
Be 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).