X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A43F4C9.8020706@gmail.com> Date: Thu, 25 Jun 2009 23:06:01 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: How to build gcc to support wchar_t and wstring on Cygwin References: <24207403.post@talk.nabble.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Mark J. Reed wrote: > On Thu, Jun 25, 2009 at 1:10 PM, Match Point >> wstring is not supported on my Cygwin 1.5.25. When I declare a >> wstring variable my g++ 3.4.4 complains wstring is undeclared. After >> reading some posted message I figured out wstring is not supported on >> Cygwin 1.5 or even 1.7. To fix this I have to rebuild entire gcc. > > No, to fix that you have to convince the newlib developers to add > wstring support to newlib. > >> _GLIBCXX_USE_WCHAR_T is still not defined. > > Cygwin does not use glibc. Whoah! Hang on there! Cygwin does indeed use newlib, not glibc; but GLIBCXX_ #defines in GCC don't relate to glibc, they relate to libstdc++-v3. cheers, DaveK -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple