public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: george.benavides@calebtech.com
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/10041: HPUX 11.0 GCC 3.2.2 does not allow _GLIBCPP_USE_WCHAR_T to be defined
Date: Wed, 12 Mar 2003 16:46:00 -0000	[thread overview]
Message-ID: <20030312164514.29280.qmail@sources.redhat.com> (raw)


>Number:         10041
>Category:       libstdc++
>Synopsis:       HPUX 11.0 GCC 3.2.2 does not allow _GLIBCPP_USE_WCHAR_T to be defined
>Confidential:   no
>Severity:       critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Mar 12 16:46:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     george.benavides@calebtech.com
>Release:        gcc 3.2.2 on HPUX
>Organization:
>Environment:

>Description:
I am trying to use 'wstring' class on HPUX. However it is not define. 

Looking at the header file 'include/bits/stringfwd.h', shows _GLIBCPP_USE_WCHAR_T is required to be defined. In file c++config.h it is not.

HPUX 11.0 standard install does have NLS support. However, I am inclined to conclude the configure scripts is requiring additional header file which are not included in a 11.0 standard install. From what I can recall ( I could be wrong) not all of the standard w*.h files are present on HP. However, all of the standard w* api calls are supported.
>How-To-Repeat:

>Fix:

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


                 reply	other threads:[~2003-03-12 16:46 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=20030312164514.29280.qmail@sources.redhat.com \
    --to=george.benavides@calebtech.com \
    --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).