This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: python binary retrieved via (cygwin) git clone does not execute - error 127


> 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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]