X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <488657A9.337C4515@dessent.net> Date: Tue, 22 Jul 2008 14:56:57 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: bernd AT prager DOT ws CC: cygwin AT cygwin DOT com Subject: Re: CYGWIN NT-5.1 1.7.0(0.185/5/ 3) wstring undeclared References: <0302154ffecb7bae3046cafb2aef9ee5 AT prager DOT ws> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com bernd AT prager DOT ws wrote: > Is that a path issue or is wstring still unsupported? Getting a functional wstring would require, at least: * implementing missing wide character I/O functions in newlib (like wprintf) * rebuilding libstdc++ so that it detects these functions and enables wstring (which means rebuilding gcc) So no, just upgrading the cygwin DLL won't change anything. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/