X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Thu, 29 Oct 2009 14:38:34 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: "Permission denied" on /usr/bin/sh when running gmake with multiple jobs
Message-ID:	<20091029133834.GO28753@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<hbn24q$gjf$1 AT ger DOT gmane DOT org> <hbs2gv$4cs$1 AT ger DOT gmane DOT org> <20091023180754 DOT GB5001 AT onderneming10 DOT xs4all DOT nl> <000001ca54a6$a1553260$e3ff9720$@com> <000001ca57dc$8b18a430$a149ec90$@com> <20091029082244 DOT GK28753 AT calimero DOT vinschen DOT de> <003901ca588a$7edc0500$7c940f00$@com>
MIME-Version:	1.0
In-Reply-To:	<003901ca588a$7edc0500$7c940f00$@com>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

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

- Raw text -