public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org To: bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, james.bannon@ntlworld.com, nobody@gcc.gnu.org Subject: Re: libstdc++/10535: No specialisations for wchar_t on cygwin Date: Fri, 16 May 2003 20:21:00 -0000 [thread overview] Message-ID: <20030516202124.4793.qmail@sources.redhat.com> (raw) Old Synopsis: No specialisations for wchar_t in std::string or std::ostream? New Synopsis: No specialisations for wchar_t on cygwin Responsible-Changed-From-To: unassigned->bkoz Responsible-Changed-By: bkoz Responsible-Changed-When: Fri May 16 20:21:24 2003 Responsible-Changed-Why: Mine. State-Changed-From-To: open->analyzed State-Changed-By: bkoz State-Changed-When: Fri May 16 20:21:24 2003 State-Changed-Why: Have you gotten any further in this effort? There is a whole long list of things that are checked at configure time before GLIBCPP_USE_WCHAR_T is defined by default: the whole list can be found in libstdc++-v3/acinclude.m4, search for the GLIBCPP_CHECK_WCHAR_T_SUPPORT macro. I'm interested in seeing how this goes. best, benjamin http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10535
reply other threads:[~2003-05-16 20:21 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030516202124.4793.qmail@sources.redhat.com \ --to=bkoz@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=james.bannon@ntlworld.com \ --cc=nobody@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).