Improve error message when freetype headers are not found using python3 #4305
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make it possible to disable the pgk-config version check even when a version is not known and use this with freetype.
This avoids trying to compare numbers to a string when the freetype version
cound not be found from headers or freetype-config. pgk-config is useless
for detecting the freetype version since it returns the libtool version and not the freetype version.
The result when freetype is not found is now (both python 2 and 3)
There is still scope for some larger improvements in the setupext.py code but these are the minimum changes needed to fix the issue reported at the mailing list here http://matplotlib.1069221.n5.nabble.com/matplotlib-devel-1-4-3-does-not-build-on-Ubuntu-14-with-python3-td45301.html
We might want to backport this to color_overhaul