On Tue, Oct 15, 2013 at 12:28:31PM +0900, nu774 wrote: > Installing libffi-devel will let python pick system libffi, so you > can skip that libffi building part you are currently stuck. > > (2013/10/15 10:10), Ryan Johnson wrote: > >"/usr/src/python3-3.3.2-3/src/Python-3.3.2/Lib/distutils/command/build_ext.py", > >line 463, in build_extensions > > self.build_extension(ext) > > File "/usr/src/python3-3.3.2-3/src/Python-3.3.2/setup.py", line 279, > >in build_extension > > if not self.configure_ctypes(ext): > > File "/usr/src/python3-3.3.2-3/src/Python-3.3.2/setup.py", line 1807, > >in configure_ctypes > > exec(f.read(), globals(), fficonfig) > > File "<string>", line 33, in <module> > >KeyError: 'X86_WIN64' > >Makefile:505: recipe for target 'sharedmods' failed > > > >At this point I'm stuck... any advice from the gurus out there would be > >appreciated.
I get the same build failure with Python 2.7.5 and 3.2.5 under 64-bit Cygwin even though I configure --with-system-ffi and have libffi-devel installed. I noticed that libffi-devel installs its headers in a non-standard location: $ cygcheck -l libffi-devel | fgrep .h /usr/lib/libffi-3.0.13/include/ffi.h /usr/lib/libffi-3.0.13/include/ffitarget.h AFAICT, this prevents Python's build system from using the system provided libffi and attempt to build its own causing an error like the one above. I can workaround the problem by creating symlinks to the libffi header files in /usr/include: $ ln -s /usr/lib/libffi-3.0.13/include/* /usr/include It appears that others have successfully built Python under 64-bit Cygwin without resorting to my workaround. Does anyone know what I'm missing? Thanks, Jason -- 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
