X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 8 Feb 2012 20:46:46 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.7.10: cygpath -p "wide char path lists not yet supported" - cygcheck.out (0/1)
Message-ID: <20120208194646.GB23481@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <jmb5j79iph129fqqfq5toj8vqk68nchooh AT 4ax DOT com> <20120208173827 DOT GQ25129 AT calimero DOT vinschen DOT de> <uke5j7lsj3rps7u23j012t3eptat0alkc9 AT 4ax DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <uke5j7lsj3rps7u23j012t3eptat0alkc9@4ax.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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 13:16, Andrew Schulman wrote:
> > 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.

THe fact that you have a .new file shows that setup tried to replace
the file after reboot.  However, the Win32 functionality, MoveFileEx
with MOVEFILE_DELAY_UNTIL_REBOOT | MOVEFILE_REPLACE_EXISTING flags
apparently doesn't work under all circumstances.  See, for instance,
http://social.msdn.microsoft.com/Search/en-US?query=PendingFileRenameOperations
for more information.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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