[issue9053] distutils compiles extensions so that Python.h cannot be found

2010-08-28 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- stage: - committed/rejected ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9053 ___ ___

[issue9053] distutils compiles extensions so that Python.h cannot be found

2010-08-27 Thread Jean-Paul Calderone
Jean-Paul Calderone inva...@example.invalid added the comment: exar...@boson:~/Projects/python-signalfd/trunk$ PYTHONPATH= ~/Projects/python/branches/py3k/python setup.py build_ext -i running build_ext building 'signalfd._signalfd' extension creating build creating build/temp.linux-i686-3.2

[issue9053] distutils compiles extensions so that Python.h cannot be found

2010-08-27 Thread Jean-Paul Calderone
Changes by Jean-Paul Calderone inva...@example.invalid: -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9053 ___

[issue9053] distutils compiles extensions so that Python.h cannot be found

2010-08-21 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: Jean-Paul, can you still reproduce the bug? According to Antoine, the configure script has seen changes but sysconfig has not been updated; this could be the source of a handful of bugs. -- nosy: +eric.araujo

[issue9053] distutils compiles extensions so that Python.h cannot be found

2010-07-31 Thread Mark Lawrence
Mark Lawrence breamore...@yahoo.co.uk added the comment: Reading msg108321 I'm setting this to 3.2. Given that the first alpha is due now shouldn't this be addressed, apologies if this has already happened but I don't know here to look? -- nosy: +BreamoreBoy versions: +Python 3.2

[issue9053] distutils compiles extensions so that Python.h cannot be found

2010-06-21 Thread Jean-Paul Calderone
New submission from Jean-Paul Calderone exar...@twistedmatrix.com: With a checkout of the py3k branch, building an extension module using distutils fails: error: Python.h: No such file or directory This is clearly because the wrong -I option is being supplied: gcc -pthread -g -O2