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 steven.daprano
Recipients benjamin.peterson, lukasz.langa, martin.panter, ncoghlan, ned.deily, steven.daprano, tds333, vstinner
Date 2016-09-13.00:37:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20160913003706.GL22471@ando.pearwood.info>
In-reply-to <1473676414.53.0.748930235735.issue28092@psf.upfronthosting.co.za>
Content
Ned, I know my system is old so I understand if 3.6 no longer supports 
gcc 4.1. Tell me what minimum version I should use (4.8?) and I'll find 
a way to upgrade or use another system.

Shouldn't the build system explicitly report that the compiler is too 
old, and suggest a minimum version, rather than just dump some random 
C-level error in the user's lap? There's a big gap between "able to run 
configure/make" and "able to diagnose configure/make errors" where users 
are currently not well provided for. It is very frustrating to deal with 
these sorts of errors especially when most of the help you get from the 
internet is "run make distclean and try again".
History
Date User Action Args
2016-09-13 00:37:13steven.dapranosetrecipients: + steven.daprano, ncoghlan, tds333, vstinner, benjamin.peterson, ned.deily, lukasz.langa, martin.panter
2016-09-13 00:37:12steven.dapranolinkissue28092 messages
2016-09-13 00:37:11steven.dapranocreate