public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc-bklyn at sneakemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/6702] requirements for wchar_t support are too restrictive for Solaris Date: Wed, 22 Mar 2006 16:04:00 -0000 [thread overview] Message-ID: <20060322160443.8045.qmail@sourceware.org> (raw) In-Reply-To: <bug-6702-4031@http.gcc.gnu.org/bugzilla/> ------- Comment #19 from gcc-bklyn at sneakemail dot com 2006-03-22 16:04 ------- This bug appears to have recurred in gcc 4.1.0. I have no wide string or iostream support on my brand-spanking-new versionof gcc, when this all worked fine with gcc 3.4.3. -- gcc-bklyn at sneakemail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gcc-bklyn at sneakemail dot | |com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6702
next parent reply other threads:[~2006-03-22 16:04 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-6702-4031@http.gcc.gnu.org/bugzilla/> 2006-03-22 16:04 ` gcc-bklyn at sneakemail dot com [this message] 2006-03-22 16:12 ` pcarlini at suse dot de 2006-03-22 16:23 ` pcarlini at suse dot de 2006-03-22 17:20 ` gcc-bklyn at sneakemail dot com 2006-03-22 17:23 ` gcc-bklyn at sneakemail dot com 2006-03-22 17:40 ` ebotcazou at gcc dot gnu dot org 2006-03-23 0:31 ` [Bug libstdc++/6702] requirements for wchar_t support are too restrictive for Solaris pre 10 pinskia at gcc dot gnu dot org 2006-03-31 14:05 ` ebotcazou at gcc dot gnu dot org 2006-04-16 9:07 ` paolo at gcc dot gnu dot org 2006-04-16 9:08 ` pcarlini at suse dot de 2006-05-03 17:00 ` paolo at gcc dot gnu dot org 2006-05-03 17:01 ` pcarlini at suse dot de 2006-05-04 19:04 ` ebotcazou at gcc dot gnu dot org [not found] <20020517102600.6702.dale@peakall.net> 2003-06-24 22:41 ` [Bug libstdc++/6702] requirements for wchar_t support are too restrictive for Solaris pinskia at physics dot uc dot edu 2003-09-25 20:51 ` bkoz at gcc dot gnu dot org 2003-10-19 7:44 ` pinskia at gcc dot gnu dot org 2003-10-19 9:51 ` pinskia at gcc dot gnu dot org 2005-09-21 16:14 ` bkoz 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=20060322160443.8045.qmail@sourceware.org \ --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).