This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ericvw
Recipients dstufft, eric.araujo, ericvw
Date 2018-06-28.19:13:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1530213218.16.0.56676864532.issue33990@psf.upfronthosting.co.za>
In-reply-to
Content
When specifying CPPFLAGS during `./configure`, `sysconfig.get_config_var('CPPFLAGS')` does capture the originally specified flags.  However, when building a C/C++ extension, any flags specified via CPPFLAGS are not present during compilation of extension source files.

Since preprocessor flags (e.g., '-I' rules) may be used during `./configure` instead of `CFLAGS`, it appears that the `CPPFLAGS` captured should also be injected when customizing the compiler executable to be invoked.

I have PR that will be submitted and linked shortly.
History
Date User Action Args
2018-06-28 19:13:38ericvwsetrecipients: + ericvw, eric.araujo, dstufft
2018-06-28 19:13:38ericvwsetmessageid: <1530213218.16.0.56676864532.issue33990@psf.upfronthosting.co.za>
2018-06-28 19:13:38ericvwlinkissue33990 messages
2018-06-28 19:13:38ericvwcreate