http://cygwin.com/acronyms/#TOFU
On Oct 29 11:25, John Daintree wrote: > Can you shed some light on http://article.gmane.org/gmane.os.cygwin/111950? > I may need to get my local cygwin build working to investigate this further. >> "J:\trunk\svn\apl\win\bin\mk_cc: >> /cygdrive/j/trunk/svn/apl/allos/bin/verbose: /usr/bin/sh: bad interpreter: >> Permission denied" Where's this Windows path coming from? Are you sure you're using only Cygwin tools? If so, get rid of the Win32 path and use either the matching /cygdrive path, or mount (the relevant subtree of) drive J to some other POSIX path. The permission denied is probably not the permission of sh itself, but the permissions of the script. It's lacking execute permissions, perhaps. If the script gets generated during the make run, it might be a race. One job tries to use the script before another job has run chmod on the script. Instead of building your own debug version of Cygwin, you could also just start with stracing your make runs and see what happens when the script access fails. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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
