➜

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 christopher.hogan
Recipients christopher.hogan
Date 2015-08-24.14:55:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1440428121.6.0.746141080033.issue24923@psf.upfronthosting.co.za>
In-reply-to
Content 
Setup.py evaluates what's given in LDFLAGS and CPPFLAGS and CFLAGS. These variables are the usual mechanism to communicate custom paths/libs/defs to a build process. However, setup.py puts system paths in front of custom paths which makes it impossible to use these variables for providing search paths to overwrite system settings.

This patch puts system paths at the end of the list to avoid this problem.  Is there a rationale for prepending system paths?
History
Date User Action Args
2015-08-24 14:55:21christopher.hogansetrecipients: + christopher.hogan
2015-08-24 14:55:21christopher.hogansetmessageid: <1440428121.6.0.746141080033.issue24923@psf.upfronthosting.co.za>
2015-08-24 14:55:21christopher.hoganlinkissue24923 messages
2015-08-24 14:55:21christopher.hogancreate