Greetings, Jason Gross! > I have some precompiled binaries (from, e.g., ocaml, gtk+). When I > install them to a location like D:\OCaml\bin and run them, the output > has a ^M at the end of every line. When I copy the binaries to a > cygwin path (something that doesn't get translated to /cygdrive/), > they work fine. This messes with all of my build scripts, which > except things like `ocamlc -where` not to have a trailing ^M. So I > tried moving them to D:\cygwin64\, and this fixed some of the > problems, but it's still broken in some cases, like when `ocamlc > -where` gives "D:/cygwin64/OCaml/lib"
> and then a build script later calls `D:/cygwin64/OCaml/bin/ocamlc -where`, > and the ^M's come back. Wait, what? WHY it calls the binary by a windows path, in first place? > It seems very broken to me that the output of an executable should > depend in this way on how it's called. If it's relevant, I updated > cygwin-x86_64 earlier today, and mount gives me > $ mount > D:/cygwin64/bin on /usr/bin type ntfs (binary,auto) > D:/cygwin64/lib on /usr/lib type ntfs (binary,auto) > D:/cygwin64 on / type ntfs (binary,auto) > C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto) > D: on /cygdrive/d type ntfs (binary,posix=0,user,noumount,auto) > E: on /cygdrive/e type ntfs (binary,posix=0,user,noumount,auto) > Y: on /cygdrive/y type afs (binary,posix=0,user,noumount,auto) > Z: on /cygdrive/z type afs (binary,posix=0,user,noumount,auto) > Anyway, I'd like to know how to fix this without manually sticking in > code to strip ^M in all of my build scripts. -- WBR, Andrey Repin (anrdae...@yandex.ru) 09.11.2013, <17:20> Sorry for my terrible english... -- 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
