[EMAIL PROTECTED] wrote: > What is odd is that there is no doubt that this file (as.exe) exists. > If I do: > ls -l > /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/as.exe > the file is listed as expected with full execute permissions set. > > If I try, from the command line, to execute the file, I get the following: > 1) If I am in the directory itself (which equates to > /usr/i686-pc-cygwin/bin), I can execute the file. > 2) If I am in any other directory, I can see the file, but I cannot execute > it (again get the "No such file or directory" error).
If you are using one of the versions of Cygwin that defaulted to traverse checking turned on, then there's a chance that this could be your problem. Though I don't know if that is possible since it works if you run it from the same directory. In order to know if this is the case we would need to know what version of Cygwin you're using, what the permissions on each component of the path to as.exe are, and whether adding 'notraverse' to $CYGWIN makes a difference. Regardless of the question of traverse checking, you should post the output of getfacl for /usr, /usr/i686-pc-cygwin, /usr/i686-pc-cygwin/bin, and /usr/i686-pc-cygwin/bin/as.exe. Incidently, much of this information would have been already known to us if you had included your "cygcheck -svr" output. If you're not going to follow the guidelines at <http://cygwin.com/problems.html> then people are going to be less likely to want to help you. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
