Issue #27 resolved

Can't install cffi on Windows

Leonard Ritter
created an issue

Using pypy setup.py develop yields the same issue.

{{{ C:\devel\cffi>pypy setup.py install running install running bdist_egg running egg_info writing requirements to cffi.egg-info\requires.txt writing cffi.egg-info\PKG-INFO writing top-level names to cffi.egg-info\top_level.txt writing dependency_links to cffi.egg-info\dependency_links.txt reading manifest file 'cffi.egg-info\SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'cffi.egg-info\SOURCES.txt' installing library code to build\bdist.win32\egg running install_lib running build_py creating build creating build\lib creating build\lib\cffi copying cffi\api.py -> build\lib\cffi copying cffi\backend_ctypes.py -> build\lib\cffi copying cffi\cparser.py -> build\lib\cffi copying cffi\ffiplatform.py -> build\lib\cffi copying cffi\gc_weakref.py -> build\lib\cffi copying cffi\model.py -> build\lib\cffi copying cffi\vengine_cpy.py -> build\lib\cffi copying cffi\vengine_gen.py -> build\lib\cffi copying cffi\verifier.py -> build\lib\cffi copying cffi__init.py -> build\lib\cffi creating build\bdist.win32 creating build\bdist.win32\egg creating build\bdist.win32\egg\cffi copying build\lib\cffi\api.py -> build\bdist.win32\egg\cffi copying build\lib\cffi\backend_ctypes.py -> build\bdist.win32\egg\cffi copying build\lib\cffi\cparser.py -> build\bdist.win32\egg\cffi copying build\lib\cffi\ffiplatform.py -> build\bdist.win32\egg\cffi copying build\lib\cffi\gc_weakref.py -> build\bdist.win32\egg\cffi copying build\lib\cffi\model.py -> build\bdist.win32\egg\cffi copying build\lib\cffi\vengine_cpy.py -> build\bdist.win32\egg\cffi copying build\lib\cffi\vengine_gen.py -> build\bdist.win32\egg\cffi copying build\lib\cffi\verifier.py -> build\bdist.win32\egg\cffi copying build\lib\cffi__init.py -> build\bdist.win32\egg\cffi byte-compiling build\bdist.win32\egg\cffi\api.py to api.pyc byte-compiling build\bdist.win32\egg\cffi\backend_ctypes.py to backend_ctypes.py c byte-compiling build\bdist.win32\egg\cffi\cparser.py to cparser.pyc byte-compiling build\bdist.win32\egg\cffi\ffiplatform.py to ffiplatform.pyc byte-compiling build\bdist.win32\egg\cffi\gc_weakref.py to gc_weakref.pyc byte-compiling build\bdist.win32\egg\cffi\model.py to model.pyc byte-compiling build\bdist.win32\egg\cffi\vengine_cpy.py to vengine_cpy.pyc byte-compiling build\bdist.win32\egg\cffi\vengine_gen.py to vengine_gen.pyc byte-compiling build\bdist.win32\egg\cffi\verifier.py to verifier.pyc byte-compiling build\bdist.win32\egg\cffi__init.py to init.pyc creating build\bdist.win32\egg\EGG-INFO copying cffi.egg-info\PKG-INFO -> build\bdist.win32\egg\EGG-INFO copying cffi.egg-info\SOURCES.txt -> build\bdist.win32\egg\EGG-INFO copying cffi.egg-info\dependency_links.txt -> build\bdist.win32\egg\EGG-INFO copying cffi.egg-info\requires.txt -> build\bdist.win32\egg\EGG-INFO copying cffi.egg-info\top_level.txt -> build\bdist.win32\egg\EGG-INFO zip_safe flag not set; analyzing archive contents... cffi.verifier: module references path__ creating dist creating 'dist\cffi-0.3-py2.7.egg' and adding 'build\bdist.win32\egg' to it removing 'build\bdist.win32\egg' (and everything under it) Processing cffi-0.3-py2.7.egg creating c:\devel\pypy\site-packages\cffi-0.3-py2.7.egg Extracting cffi-0.3-py2.7.egg to c:\devel\pypy\site-packages Removing cffi 0.3 from easy-install.pth file Adding cffi 0.3 to easy-install.pth file

Installed c:\devel\pypy\site-packages\cffi-0.3-py2.7.egg Processing dependencies for cffi==0.3 Searching for pycparser Reading http://pypi.python.org/simple/pycparser/ Reading http://code.google.com/p/pycparser/ Best match: pycparser 2.08 Downloading http://pypi.python.org/packages/source/p/pycparser/pycparser-2.08.ta r.gz#md5=923f08a99839b4fac45d2ac395e1ef7e Processing pycparser-2.08.tar.gz Writing c:\users\lritter\appdata\local\temp\easy_install-n99ik1\pycparser-2.08\s etup.cfg Running pycparser-2.08\setup.py -q bdist_egg --dist-dir c:\users\lritter\appdata \local\temp\easy_install-n99ik1\pycparser-2.08\egg-dist-tmp-nlkyak zip_safe flag not set; analyzing archive contents... No eggs found in c:\users\lritter\appdata\local\temp\easy_install-n99ik1\pycpars er-2.08\egg-dist-tmp-nlkyak (setup script problem?) error: Could not find required distribution pycparser }}}

Comments (6)

  1. Leonard Ritter reporter

    This problem still persists, with the latest pycparser-2.09.1. Output of today:

    C:\devel\cffi>pypy setup.py develop
    running develop
    running egg_info
    writing requirements to cffi.egg-info\requires.txt
    writing cffi.egg-info\PKG-INFO
    writing top-level names to cffi.egg-info\top_level.txt
    writing dependency_links to cffi.egg-info\dependency_links.txt
    reading manifest file 'cffi.egg-info\SOURCES.txt'
    reading manifest template 'MANIFEST.in'
    writing manifest file 'cffi.egg-info\SOURCES.txt'
    running build_ext
    Creating c:\devel\pypy\site-packages\cffi.egg-link (link to .)
    Adding cffi 0.5 to easy-install.pth file
    
    Installed c:\devel\cffi
    Processing dependencies for cffi==0.5
    Searching for pycparser
    Reading http://pypi.python.org/simple/pycparser/
    Reading https://bitbucket.org/eliben/pycparser
    Reading http://code.google.com/p/pycparser/
    Best match: pycparser 2.09.1
    Downloading http://pypi.python.org/packages/source/p/pycparser/pycparser-2.09.1.
    tar.gz#md5=74aa075fc28b7c24a4426574d1ac91e0
    Processing pycparser-2.09.1.tar.gz
    Writing c:\users\lritter\appdata\local\temp\easy_install-nyogwk\pycparser-2.09.1
    \setup.cfg
    Running pycparser-2.09.1\setup.py -q bdist_egg --dist-dir c:\users\lritter\appda
    ta\local\temp\easy_install-nyogwk\pycparser-2.09.1\egg-dist-tmp-yub16y
    zip_safe flag not set; analyzing archive contents...
    No eggs found in c:\users\lritter\appdata\local\temp\easy_install-nyogwk\pycpars
    er-2.09.1\egg-dist-tmp-yub16y (setup script problem?)
    error: Could not find required distribution pycparser
    
  2. Armin Rigo

    Fwiw I've successfully installed and tested cffi on Windows, once for every release. I did not try "setup.py develop" though, only "setup.py install".

  3. anatoly techtonik

    I may miss something obvious, but it looks like for every release there should be a release table, like:

                      VS 2010 |   MinGW   | ...
    ---------------------------------------------------
    Windows 32 |    installs  |   fails
    Windows 64 |       ...    |     ...
    
  4. Log in to comment