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 njs
Recipients benjamin.peterson, lukasz.langa, martin.panter, ncoghlan, ned.deily, njs, rgbecker, steven.daprano, tds333, vstinner
Date 2016-10-13.17:45:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1476380759.41.0.225322875342.issue28092@psf.upfronthosting.co.za>
In-reply-to
Content
> Would it be possible to upgrade the "manylinux" compiler (take a more recent GCC version)?

No, it's possible :-(. 4.8.2 is the very most modern version of GCC you can use if you want to build binaries to run on CentOS/RHEL 5. (And "binaries should run on CentOS/RHEL 5" is the definition of manylinux1.)

I am a bit confused that gcc 4.8.2 is having trouble with cpython 3.6.0b2, though -- supposedly anything newer than gcc 4.3 should be fine with it. And yet. One possibility is that something funny is going on inside the build scripts Robin's using and that Python's ./configure is somehow finding and using the platform compiler (gcc 4.1) even though the first "gcc" in $PATH is 4.8.2, which would make this a false alarm.
History
Date User Action Args
2016-10-13 17:45:59njssetrecipients: + njs, rgbecker, ncoghlan, tds333, vstinner, benjamin.peterson, ned.deily, steven.daprano, lukasz.langa, martin.panter
2016-10-13 17:45:59njssetmessageid: <1476380759.41.0.225322875342.issue28092@psf.upfronthosting.co.za>
2016-10-13 17:45:59njslinkissue28092 messages
2016-10-13 17:45:59njscreate