Issue 14292: OS X installer build script doesn't set $CXX, so it ends up as "c++" (original) (raw)

Issue14292

Created on 2012-03-13 20:44 by nicholas.riley, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (4)
msg155663 - (view)	Author: Nicholas Riley (nicholas.riley) *	Date: 2012-03-13 20:44
% python build-installer.py \ --sdk-path=/Developer/SDKs/MacOSX10.6.sdk \ --universal-archs=intel \ --dep-target=10.6 Settings: * Source directory: /Users/nicholas/src/cpython * Build directory: /tmp/_py * SDK location: /Developer/SDKs/MacOSX10.6.sdk * Third-party source: /tmp/_py/third-party * Deployment target: 10.6 * Universal architectures: ('i386', 'x86_64') * C compiler: gcc-4.2 [...] Building a universal python for intel architectures [...] checking for c++... c++ configure: WARNING: By default, distutils will build C++ extension modules with "c++". If this is not intended, then set CXX on the configure command line.
msg168851 - (view)	Author: Ronald Oussoren (ronaldoussoren) *	Date: 2012-08-22 07:52
The attached patch sets not just 'CC' but 'CXX' as well. I haven't tested the patch beyond building on an OSX 10.8 system (that is, the primary use of the script is not tested)
msg168925 - (view)	Author: Roundup Robot (python-dev)	Date: 2012-08-23 06:36
New changeset 1f27572a10ce by Ned Deily in branch 'default': Issue #14292: Ensure that the OS X installer build configures the CXX http://hg.python.org/cpython/rev/1f27572a10ce
msg168927 - (view)	Author: Ned Deily (ned.deily) *	Date: 2012-08-23 06:44
Fix applied for 3.3.0. All build-installer fixes will be backported for 2.7.4 and 3.2.4.