Hello, Thank you for the information, this helped me formulate a solution.
Best, - TTimo On Tue, Jun 28, 2022 at 10:20 AM Andrey Repin <anrdae...@yandex.ru> wrote: > Greetings, Timothee Besset! > > > Hello, > > > We are seeing some odd behavior from cygpath.exe when it is copied and > used > > outside the normal cygwin installation directory: > > > PS C:\Users\ttimo> C:\cygwin64\bin\cygpath.exe -a -u "C:" > > /cygdrive/c > > To begin with, "C:" means "current working directory on drive 'C:'". Not > "root > directory of 'C:'". > The behavior of cygpath is incorrect in this case. > > > After copying cygpath.exe and cygwin1.dll to a blank C:\tmp: > > Both must be in '…/bin' directory, this is user error. > > > PS C:\Users\ttimo> C:\tmp\cygpath.exe -a -u "C:" > > / > > > (should be /cygdrive/c!) > > No? See above. > > > After copying those same files to C:\tmp\tmp: > > > PS C:\Users\ttimo> C:\tmp\tmp\cygpath.exe -a -u "C:" > > /cygdrive/c > > > It works again! > > By coincidence. (And no.) > > > We bundle a few cygwin pieces (ssh, rsync) in our application and run > them > > on machines that may not have cygwin installed, this is why we are trying > > to use cygpath outside a normal installation directory - see > > https://gitlab.steamos.cloud/devkit/steamos-devkit for details. > > See above, cygwin tools' layout must follow FHS, or you will see all sorts > of > issues. > That aside, you could always use /proc/cygdrive/ root for manual path > conversion. > > > We've been using this setup for more than a year and only noticing this > > now; I suspect this used to work fine but I couldn't tell you of an older > > version that worked for sure. > > Um, no. > > > -- > With best regards, > Andrey Repin > Tuesday, June 28, 2022 11:14:52 > > Sorry for my terrible english... -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple