This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: python binary retrieved via (cygwin) git clone does not execute - error 127
- From: Duane Ellis <duane at duaneellis dot com>
- To: Rick Springob <rspringob at gmail dot com>
- Cc: cygwin at cygwin dot com
- Date: Wed, 24 Jun 2015 08:18:33 -0700
- Subject: Re: python binary retrieved via (cygwin) git clone does not execute - error 127
- Authentication-results: sourceware.org; auth=none
- References: <loom dot 20150624T153415-310 at post dot gmane dot org>
> 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