X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=V/eBB3Muwe5sOnDhxlA+YMyU23a1
	+gBLmttUOtV/lmCozAffvXKS7EpLwZwe78JpEKgKiJO5Eb5Qg2f1ckJ/uplAnGCt
	Hud0aGvd/wjnvR3O0tTiGR+dgEFY9SunDrzuq3LnttqUA4Ybtbl7JladH9437IoQ
	yzeh+gBSIWSGCWc=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; s=default; bh=HdRKwZqnUlf3kOa1ze0BaMlKhIk=; b=xS
	WrokXHJkzWoAAdLzysCjI/eKAn/wdglFCko+Srrncb1zVemA5cVukbeeasMzZHFy
	vK3FBfQXSScpnJhD/xEWnSl1FmWrVGzypEdw5Ob+icLArVPe0Nn/AkfQZ+jiLoIg
	IYrYoX9p6ByfM/K+elT7t+DqRpqUWrLLgHDBnZmkY=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=1.5 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=Larry, Hall, Young, Warren
X-HELO:	etr-usa.com
Mime-Version:	1.0 (Mac OS X Mail 8.2 \(2104\))
Subject:	Re: Running native exe from Cygwin in random instances reports incorrect error code 127
From:	Warren Young <wyml AT etr-usa DOT com>
In-Reply-To:	<569DA37A.6090509@cygwin.com>
Date:	Tue, 19 Jan 2016 15:40:43 -0700
Message-Id:	<EEAE9AFA-85A6-4649-9908-4963E59B8A67@etr-usa.com>
References:	<CAGW0ud2ELnAAkx57A3LutxiAoBtv1Mm7ssfaut__JDJu5GUSkg AT mail DOT gmail DOT com> <C12B9B32-5A3A-4F9B-A8FD-BC8F3EE91F0F AT etr-usa DOT com> <569DA37A DOT 6090509 AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id u0JMf69q032640

On Jan 18, 2016, at 7:46 PM, Larry Hall (Cygwin) <reply-to-list-only-lh AT cygwin DOT com> wrote:
> 
> On 01/18/2016 02:50 PM, Warren Young wrote:
> 
>> If this pair of programs *fails* on your system, then you’ve probably got a BLODA problem:
>> 
>>     https://cygwin.com/faq/faq.html#faq.using.bloda
> 
> The somewhat coincidental recent thread below makes me bet on BLODA,
> particularly if it's only happening sometimes.  I could see BLODA
> blocking access to a needed DLL in some cases just at the wrong time,
> resulting in a code 127.

The other thread is basically reporting a known weirdness on Windows, which is that DLLs require the executable flag to be set in its ACL, else it can’t be loaded into an EXE.  In Cygwin, we see this as a missing ‘x’ bit in ls -l output.

It’s not precisely a Cygwin problem, but we do see it sometimes in software built with Cygwin which comes from an *ix system, where libfoo.{so,a} doesn’t require chmod +x to be loaded into an executable.  When ported, the build system doesn’t do the right thing on Cygwin, so it fails.

I assume it’s portability software such as libtool and cmake that are fixing up this detail for most software ported from *ix to Cygwin.

But yes, you’re right, a BLODA misstep could cause a DLL to fail to load, causing a lookalike symptom even though the actual cause is different.
--
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 -