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:cc:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=CdhonCF+m7TmBzrmwL+R0E9vROqx
	SY6NZRWcQCKNfL+E9otLfZ7gzIc9LXz4siIl6V/KuFZEvmDAREPB5w21QGB5EQ3y
	5F0MLDBbdidPETUBGZpa0SnTbz1zuvbUM3diXDgUgkvXW57Knt/icqIa0EZ0+ZXA
	BByUPC3PlERtU0Y=
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:cc:content-transfer-encoding:message-id
	:references:to; s=default; bh=u9a/obZiXUD/OMdqrEUqGYA4kzM=; b=U4
	YgIYOc6wJqyyrEek66OoEKGiSvPndADcEY1WHs0P6Gqhp3V5xO0BADIppJc4Oc7n
	oCUZDFBA81rXWxqq1L0AFNMnCI+0Q239pCFS4AS3j7qTs9v6dxWVkViajpbKs/27
	QKoACEk9CyTjFPv4Q9oLb2ojLTuqKFqsGW/lDy9Hg=
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.0 required=5.0 tests=AWL,BAYES_20,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2
X-HELO: p3plsmtpa08-09.prod.phx3.secureserver.net
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Subject: Re: python binary retrieved via (cygwin) git clone does not execute - error 127
From: Duane Ellis <duane AT duaneellis DOT com>
In-Reply-To: <loom.20150624T153415-310@post.gmane.org>
Date: Wed, 24 Jun 2015 08:18:33 -0700
Cc: cygwin AT cygwin DOT com
Message-Id: <FABB9FE6-2341-42F1-8EAB-2C0E3E657AA4@duaneellis.com>
References: <loom DOT 20150624T153415-310 AT post DOT gmane DOT org>
To: Rick Springob <rspringob AT gmail DOT com>
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t5OFIl9j018321

> The problem has only been seen with the git 
> that ships with 64-bit cygwin.

Use “ldd” - against the executable, determine the exact file (absolute path) of every dll that is used/required.

Including any missing DLLs.

You might also need to walk through your “Python Library” (where all of the python loadable modules are stored)
Remember: LDD will only tell you the DLLs that are used, it will not tell you about the modules that are loaded.

Use a “DLL Explorer” program to determine exactly what type of DLL  (32bit or 64bit) of each DLL.
Examples: Dependancy Walker, ‘DumpBin” - there are a number of tools that help

Painful process :-(  I have ran into this many times with other things.

have also run into problems with Python DLLs built with different versions of Visual Studio.
(The C runtime library is different)

In the end, I have had to put a shell wrapper around Python - so that it would *change/reset” various Python ENV variables.

With multiple versions of python (32,64, 2.7, 3.0, windows, cygwin, local-build) nothing is consistent.

Again painful.




--
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