[pypy-issue] Issue #1905: pypy does not add system-wide headers to CFLAGS if installed in a virtualenv (pypy/pypy)

Felix Schwarz issues-reply at bitbucket.org
Mon Oct 27 14:42:24 CET 2014


New issue 1905: pypy does not add system-wide headers to CFLAGS if installed in a virtualenv
https://bitbucket.org/pypy/pypy/issue/1905/pypy-does-not-add-system-wide-headers-to

Felix Schwarz:

I created a virtualenv with pypy as documented in the [docs](http://pypy.readthedocs.org/en/latest/install.html#installing-using-virtualenv).

However afterwards I was unable to compile lxml 3.4.0 (tar.gz from pypi) because pypy didn't find pyconfig.h. pyconfig.h is installed through pypy-devel in /usr/lib64/pypy-2.2.1

    building 'lxml.etree' extension
    cc -O2 -fPIC -Wimplicit -I/usr/include/libxml2
    -I<…>/lxml-3.4.0/src/lxml/includes
    -I<…>/venv.pypy/include -c src/lxml/lxml.etree.c -o
    build/temp.linux-x86_64-2.7/src/lxml/lxml.etree.o -w
    src/lxml/lxml.etree.c:8:22: fatal error: pyconfig.h: No such file or directory
     #include "pyconfig.h"
                          ^
    compilation terminated.
    error: command 'cc' failed with exit status 1

As you can see only "venv.pypy/include" is added via the cflags but not my system-wide directory. This works if I used the system-wide pypy.

I think pypy should match cpython's behavior and include the system-wide headers even when installed in a virtualenv.




More information about the pypy-issue mailing list