From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1819 invoked by alias); 3 Oct 2002 19:09:07 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 1676 invoked from network); 3 Oct 2002 19:09:05 -0000 Received: from unknown (HELO gnome.softbook.com) (208.211.82.130) by sources.redhat.com with SMTP; 3 Oct 2002 19:09:05 -0000 Received: from [208.211.82.160] (dhcp0.softbook.com [208.211.82.160]) (authenticated bits=0) by gnome.softbook.com (8.12.1/8.12.1) with ESMTP id g93IxETD013362 for ; Thu, 3 Oct 2002 11:59:15 -0700 (PDT) User-Agent: Microsoft-Entourage/9.0.2509 Date: Thu, 03 Oct 2002 12:09:00 -0000 Subject: Re: wstring and gcc From: andy To: Message-ID: In-Reply-To: <3D9C7C71.64FEAF72@centropolisfx.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-SW-Source: 2002-10/txt/msg00034.txt.bz2 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