From: andy <andy@softbook.com>
To: <gcc-help@gcc.gnu.org>
Subject: Re: wstring and gcc
Date: Thu, 03 Oct 2002 12:09:00 -0000 [thread overview]
Message-ID: <B9C1E3DC.7215%andy@softbook.com> (raw)
In-Reply-To: <3D9C7C71.64FEAF72@centropolisfx.com>
The wide char support is determined by the system, I believe.
The configure script looks for wchar support in the system headers and turns
off the libc++ macros if it doesn't find it there.
In my particular case, I'm on a machine with a rather old kernel and I
installed gcc3 in my home directory and not in /usr
So maybe a combination of the above resulted in the problem
Andy
On 10/3/02 10:20 AM, "Gokhan Kisacikoglu" wrote:
> andy wrote:
>>
>> I got it to work.Basicaly, I just needed to enable wchar support in
>> libstdc++.
>
>
> Does this mean you can either use the wide or normal characters, or
> simply it is an configuration issue to support them both?
>
> Gokhan
prev parent reply other threads:[~2002-10-03 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 11:30 andy
2002-09-29 16:16 ` andy
2002-09-30 8:15 ` Gokhan Kisacikoglu
2002-10-03 9:21 ` andy
2002-10-03 10:22 ` Gokhan Kisacikoglu
2002-10-03 12:09 ` andy [this message]
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=B9C1E3DC.7215%andy@softbook.com \
--to=andy@softbook.com \
--cc=gcc-help@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).