Dear folks!
The command 'cygpath -am .' yields different results between
cygwin-3.1.4-1 and cygwin-3.3.2-1 on a Windows 10 box when the current
directory is a network share.
Example with V3.1.4:
cygpath -am . ---> P:/mytool/gbuild/wintel/libtiff
Example with V3.3.2-1
cygpath -am . ---> //mynas.mydomain.de/product/mytool/gbuild/wintel/libtiff
This causes UNC filenames to appear and this cmd.exe is unable to start
in those directories when started from a cygwin shell or from nmake run
in a cygwin shell.
I prefer to get the old behaviour back since it worked for 20+ years up
to now - or at least an option to enable the old behavior again.
Please note that I have not subscribed to any cygwin mailing list.
Thanks in advance and best regards
Wolfgang
--
Wolfgang Kechel mailto:wolfgang.kec...@prs.de
Patzschke + Rasp Software GmbH http://www.prs.de
Bierstadter Straße 7 Fax: +49-(0)611-1731-31
D-65189 Wiesbaden Phone: +49-(0)611-1731-611 / +49-(0)174-3454260
Patzschke + Rasp Software GmbH, Bierstadter Str. 7, D-65189 Wiesbaden
Eintragung im Handelsregister: Amtsgericht Wiesbaden, HRB Nr. 22673
Geschäftsführer: Wolfgang Kechel, Till Immanuel Patzschke
--
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
