public inbox for
help / color / mirror / Atom feed
From: Phil Edwards <>
Subject: Re: libstdc++/6702: requirements for wchar_t support are too restrictive
Date: Fri, 17 May 2002 11:06:00 -0000	[thread overview]
Message-ID: <> (raw)

The following reply was made to PR libstdc++/6702; it has been noted by GNATS.

From: Phil Edwards <>
Subject: Re: libstdc++/6702: requirements for wchar_t support are too restrictive
Date: Fri, 17 May 2002 14:00:15 -0400

 On Fri, May 17, 2002 at 05:19:38PM -0000, wrote:
 > config.h and c++config.h to
 > define _GLIBCPP_USE_WCHAR_T and rebuilding libstdc++ works without problem
 > on solaris 8, although autoconf had decided that this wasn't possible.
 Before you try hacking around this yourself, it's useful to investigate
 /why/ the autoconf scripts decided it wasn't possible.  The file
 sparc-sun-solaris2.8/libstdc++-v3/config.log in the build directory will
 contain the output of the wide-character tests.  Searching for "C99",
 "mbstate_t" and "wchar" should give results.
 > Support for wchar_t is mandated by the C++ standard - gcc should make
 > more extensive efforts to support it on any platform that it reasonably can
 > (i.e. supports the set of functions used by libstdc++).
 We already try, thankyouverymuch.  More specifically, others have reported
 success on this platform, so I'm initially inclined to look at individual
 platform problems than systemic bugs.  There were problems with the 'long
 long' tests under Solaris giving up too easily, but those were fixed back
 in 3.0.3; wide character support is related but separate.

             reply	other threads:[~2002-05-17 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-17 11:06 Phil Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 17:36 Dara Hazeghi
2003-05-14 17:36 Dara Hazeghi
2003-05-12 10:54 steven
2003-05-10 23:56 Dara Hazeghi
2002-05-17 10:26 dale

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

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