Unless the install script is suing to another user during the install, the problem is not that I don't have write access to /usr/bin. My workaround was to change the value of INSTALLSITESCRIPT to /usr/bin_00, and then move the files after the make install. Since the files are now happily installed in /usr/bin, I must have write access...
No I suspect that because cygwin is doing some dark magic linking /usr/bin to /bin, somewhere along the line there's some code like:
if( not -d $dir ) {
mkdir($dir) or die("can't create $dir because you don't have write p
+ermission")
}
and that -d test is failing because /usr/bin isn't really truly a directory.
Interestingly, if I change the Makefile to point to /usr/bin_00 and then install, the install works ok, even twice. So for some reason the install is not trying to create /usr/bin_00 the second time (even if I delete the scripts installed).
