RE: winsup\cygwin\path.cc issues

2018-05-29 Thread Ken Harris
-Original Message- From: Corinna Vinschen [mailto:corinna-cyg...@cygwin.com] Sent: Tuesday, May 29, 2018 12:32 PM To: cygwin@cygwin.com Cc: Ken Harris Subject: Re: winsup\cygwin\path.cc issues Hi Ken, On May 4 01:23, Ken Harris wrote: > Hi Marco: Sorry for not replying to the original

Re: winsup\cygwin\path.cc issues

2018-05-29 Thread Corinna Vinschen
Hi Ken, On May 4 01:23, Ken Harris wrote: > Hi Marco: Sorry for not replying to the original exchange we had. I > wasn't subscribed to the list but now I am so it won't happen again > (so I'm quoting our exchange below). > > I installed and built cygwin1.dll with

Re: winsup\cygwin\path.cc issues

2018-05-03 Thread Ken Harris
Hi Marco: Sorry for not replying to the original exchange we had. I wasn't subscribed to the list but now I am so it won't happen again (so I'm quoting our exchange below). I installed and built cygwin1.dll with an added assert in path.cc to ident

Re: winsup\cygwin\path.cc issues

2018-05-02 Thread Marco Atzeri
On 5/2/2018 3:49 PM, Ken Harris wrote: Hi: While originally investigating a sporadic failure in MSYS2, I believe I found that its origin may actually be within Cygwin. Given the following command sequence on cygwin64 in a CMD.EXE command prompt (on Windows 10

winsup\cygwin\path.cc issues

2018-05-02 Thread Ken Harris
Hi: While originally investigating a sporadic failure in MSYS2, I believe I found that its origin may actually be within Cygwin. Given the following command sequence on cygwin64 in a CMD.EXE command prompt (on Windows 10 x64 if it matters). cd C:\Cygwin64\bin