From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6923 invoked by alias); 20 Mar 2004 02:56:34 -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 6910 invoked from network); 20 Mar 2004 02:56:33 -0000 Received: from unknown (HELO mgr2.xmission.com) (198.60.22.202) by sources.redhat.com with SMTP; 20 Mar 2004 02:56:33 -0000 Received: from [198.60.22.201] (helo=mgr1.xmission.com) by mgr2.xmission.com with esmtp (Exim 3.35 #1) id 1B4Wf2-0006bn-02; Fri, 19 Mar 2004 19:56:32 -0700 Received: from [198.60.22.20] (helo=xmission.xmission.com) by mgr1.xmission.com with esmtp (Exim 4.30) id 1B4Wf2-0004Sz-Qh; Fri, 19 Mar 2004 19:56:32 -0700 Received: from llewelly by xmission.xmission.com with local (Exim 3.35 #1 (Debian)) id 1B4Wf2-0004ff-00; Fri, 19 Mar 2004 19:56:32 -0700 To: Cc: "GCC" References: <20040320014141.B18D8109A17@earth-ox.its.caltech.edu> From: llewelly@xmission.com Date: Sat, 20 Mar 2004 05:00:00 -0000 In-Reply-To: <20040320014141.B18D8109A17@earth-ox.its.caltech.edu> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 MIME-Version: 1.0 Subject: Re: Failure crossing gcc 3.3.3 from GNU/Linux to MinGW Content-Type: text/plain; charset=us-ascii X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mgr1.xmission.com X-Spam-Level: X-Spam-Status: No, hits=0.3 required=8.0 tests=NO_REAL_NAME autolearn=no version=2.63 X-SA-Exim-Mail-From: llewelly@xmission.com X-SA-Exim-Version: 3.1 (built Wed Aug 20 09:38:54 PDT 2003) X-SA-Exim-Scanned: Yes X-SW-Source: 2004-03/txt/msg01196.txt.bz2 "Stephan T. Lavavej" writes: > 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? I think you want to add --disable-c-mbchar to your configure line for gcc. See http://gcc.gnu.org/onlinedocs/libstdc++/configopts.html However I don't have a cygwin system to test this on. There are two caveats to this flag: (a) it makes a libstdc++ without wchar support and therefor farther from the ISO standard, and (b) C++ built with a --disable-c-mbchar configured compiler may not be linkable with code built with a --enable-c-mbchar compiler.