X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0	tests=AWL,BAYES_00,SPF_HELO_PASS,TW_YG,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Andrew Schulman <schulman DOT andrew AT epamail DOT epa DOT gov>
Subject: Re: 1.7.10: cygpath -p "wide char path lists not yet supported" - cygcheck.out (0/1)
Date: Wed, 08 Feb 2012 13:16:37 -0500
Lines: 22
Message-ID: <uke5j7lsj3rps7u23j012t3eptat0alkc9@4ax.com>
References: <jmb5j79iph129fqqfq5toj8vqk68nchooh AT 4ax DOT com> <20120208173827 DOT GQ25129 AT calimero DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Archive: encrypt
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

> On Feb  8 12:22, Andrew Schulman wrote:
> > $ cygpath -u 'C:\WINDOWS'
> > /win/c/WINDOWS
> > 
> > $ cygpath -pu 'C:\WINDOWS'
> >      15 [main] cygpath 5076 C:\cygwin\bin\cygpath.exe: *** fatal error - wide char path lists not
> > yet supported
> > Hangup
> 
> Try `uname -r'

Erf, thanks.  I had updated to 1.7.10, but as you guessed, uname -r said 1.7.9.

BTW, after restarting all Cygwin process, uname -r still said 1.7.9.  So I rebooted; still 1.7.9. So
I looked in c:\cygwin\bin, and found that cygwin1.dll was still version 1.7.9, but there was also
cygwin1.dll.new, version 1.7.10.  So I removed cygwin1.dll and renamed cygwin1.dll.new, and now I'm
running 1.7.10.

Is that the expected behavior for setup?  I assume that I had left some Cygwin processes running
when I updated to 1.7.10.  I don't remember setup warning me about replacing files in use, although
maybe it did and I forgot.  But I thought the problem was supposed to take care of itself after a
reboot - I don't remember ever encountering cygwin1.dll.new before.


--
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