Robert P Fischer added the comment:
Could this be fixed on 3.5 and 3.6?
On Fri, Feb 12, 2016 at 2:34 PM, Terry J. Reedy <rep...@bugs.python.org>
wrote:
>
> Terry J. Reedy added the comment:
>
> 3.4 only gets security fixes
>
> --
> nosy: +terry.reedy
>
Robert P Fischer added the comment:
> The makefiles use CC throughout and don't look at and OBJC variable. Is
> that variable a standard way to specify an ObjC compiler in makefiles?
I believe that OBJC and OBJCFLAGS are standard for Autoconf/Automake:
https://www.gnu.org/software/au
Robert P Fischer added the comment:
I'm trying to compile the Objective-C portions of Python (the Python
Launcher app) with clang, not GCC. Why does Python insist on using GCC,
even when I set the OBJC env variable to clang? That seems to be a problem
that the Python project CAN fix.
On Tue
New submission from Robert P Fischer:
Changes to OS X 10.11 render GCC's Objective-C compiler useless. However, I
want to compile the main part of Python in GCC (because my C++ / Fortran Cython
modules use GCC).
I tried to build Python (via MacPorts) using Clang for Objective-C and GCC
