Thanks for the reply. Some thoughts: >Please use Cygwin paths with Cygwin tools. >Windows paths are not guaranteed to work with every Cygwin tool.
This is scripted, and while I can hack it to use Cygwin paths, it probably shouldn't be lying to me, saying that it worked. And it did work before, still does with older Cygwin (on another machine). >What you are doing may or may not work, depends, if you are using Cygwin or >native Subversion client. >In either case, it isn't very bright idea to enforce POSIX access mask outside >Cygwin tree, unless you know what you are doing and absolutely need it. >From your description, you don't need it at all. I'm not actually trying to enforce POSIX anything--I'm trying to be able to read the build artifacts, which were put there via mv and cp. The compiler is native Windows, isn't creating the artifacts with any special permissions. So there's actually another mystery, which is why the artifacts don't have the right permissions in the first place. With the cobbled-together environment (CMake, the Dignus compiler, Cygwin) this may not be really diagnosable, I realized. I was hoping that there was some clue in the fact that the path makes a difference. SVN client is Tortoise. I have done a fresh checkout and the problem persists, so it isn't some weirdness with a tainted file in the source tree, I don't think. -- 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
