From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16613 invoked by alias); 20 Mar 2004 01:41:45 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 16592 invoked from network); 20 Mar 2004 01:41:43 -0000 Received: from unknown (HELO outgoing-mail.its.caltech.edu) (131.215.49.69) by sources.redhat.com with SMTP; 20 Mar 2004 01:41:43 -0000 Received: from water-dog (water-dog [192.168.1.26]) by water-ox-postvirus (Postfix) with ESMTP id 9554326AC9E for ; Fri, 19 Mar 2004 17:41:42 -0800 (PST) Received: from earth-ox ([192.168.1.9]) by water-dog (MailMonitor for SMTP v1.2.2 ) ; Fri, 19 Mar 2004 17:41:41 -0800 (PST) Received: from northwood (northwood.caltech.edu [131.215.159.60]) by earth-ox.its.caltech.edu (Postfix) with ESMTP id B18D8109A17 for ; Fri, 19 Mar 2004 17:41:41 -0800 (PST) Reply-To: From: "Stephan T. Lavavej" To: "GCC" Subject: Re: Failure crossing gcc 3.3.3 from GNU/Linux to MinGW Date: Sat, 20 Mar 2004 04:53:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20040320014141.B18D8109A17@earth-ox.its.caltech.edu> X-Spam-Status: No, hits=0.0 tagged_above=-100000.0 required=5.0 X-Spam-Level: X-SW-Source: 2004-03/txt/msg01195.txt.bz2 Thanks for the reply. [Gabriel Dos Reis] > As you probably know, in the nutshell, native builds on MinGW > or Cygwin do not have support for wchar_t so corresponding > support in libstdc++ is disabled. It looks like when > building the cross, you did -not- take that fact into > consideration and somehow requested support for wchar_t while > the underlying C functions are missing. But how did I do that? In my build script, I configure cross binutils, cross gcc, and crossed-native gcc with --disable-nls. Or does that not affect wchar gunk at all? How can I disable the wchar stuff explicitly? Stephan T. Lavavej