[issue6957] Extension modules fail to build on OS X 10.6 using python.org 2.x/3.x

Ronald Oussoren added the comment: Committed in r75147 (trunk) and r75148 (2.6) -- status: open -> closed ___ Python tracker ___ ___ P

[issue6957] Extension modules fail to build on OS X 10.6 using python.org 2.x/3.x

Barry A. Warsaw added the comment: Please apply this for 2.6.3rc1 -- priority: -> release blocker resolution: -> accepted ___ Python tracker ___ ___

[issue6957] Extension modules fail to build on OS X 10.6 using python.org 2.x/3.x

Ned Deily added the comment: Explicitly defining CC during the installer build does seem to fix the extension build problem, at least for well-behaved extensions. I successfully tested building simplejson (using both easy_install and direct setup.py installs) and MySQLdb, both on 10.6 using

[issue6957] Extension modules fail to build on OS X 10.6 using python.org 2.x/3.x

Ned Deily added the comment: > (that is, assuming the remaining builds and tests in progress complete normally - I'll update the status when they finish) No regressions noted: - DEPTARGET=10.3, 2-way i386/ppc, built on 10.5: regrtest on 10.4 ppc, 10.5 ppc, 10.6 i386 - DEPTARGET=10.3, 2-w

[issue6957] Extension modules fail to build on OS X 10.6 using python.org 2.x/3.x

Ronald Oussoren added the comment: r75022 (trunk) and r75023 (2.6) add the other half of my proposal: distutils will ignore -isysroot SDKPATH when SDKPATH is not present on the current system. That combined with explicit compilation using gcc-4.0 should solve these build issues with the OSX

[issue6957] Extension modules fail to build on OS X 10.6 using python.org 2.x/3.x

Ronald Oussoren added the comment: There is a much easier solution for the 2.6.3 release: ensure that CC=gcc- 4.0 when building the installer. That requires minimal changes to the build machinery and should be safe enough. The only change to distutils I do want to make for 2.6.3 is to detect

[issue6957] Extension modules fail to build on OS X 10.6 using python.org 2.x/3.x

Ned Deily added the comment: Tweaking distutils as you propose sounds like a good idea to help with future releases. Also, the proposed installer variant to support 64-bit would not have this problem as it would only work with 10.5 and above. (Perhaps there's a warning in all this that tryi

[issue6957] Extension modules fail to build on OS X 10.6 using python.org 2.x/3.x

Ronald Oussoren added the comment: It should be possible to tweak distutils to do the right thing for upcoming releases, distutils already contains some special code to allow building extensions for a univeral build on 10.3.9 (where the compiler doesn't support universal builds at all) and we

[issue6957] Extension modules fail to build on OS X 10.6 using python.org 2.x/3.x

Changes by Ned Deily : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/ma

[issue6957] Extension modules fail to build on OS X 10.6 using python.org 2.x/3.x

New submission from Ned Deily : Potential 2.6.3 release blocker On OS X 10.6 (Snow Leopard), if you attempt to install a package with a extension module using a Python from a python.org OS X installer (say, 2.6.x or 3.1.x), the c compilation steps will likely fail in one of two ways: 1. Rece