public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dale@peakall.net
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/6702: requirements for wchar_t support are too restrictive
Date: Fri, 17 May 2002 10:26:00 -0000	[thread overview]
Message-ID: <20020517171938.9805.qmail@sources.redhat.com> (raw)


>Number:         6702
>Category:       libstdc++
>Synopsis:       requirements for wchar_t support are too restrictive
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri May 17 10:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Dale Peakall
>Release:        3.1 20020510 (prerelease)
>Organization:
>Environment:
solaris 8
>Description:
The requirements before libstdc++ will build with support
for wchar_t are too restrictive.

Changing cwchar and cwctype to not try import the missing
functions into std namespace and changing 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.

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++).
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


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

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

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=20020517171938.9805.qmail@sources.redhat.com \
    --to=dale@peakall.net \
    --cc=gcc-gnats@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).