[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Ned Deily added the comment: New changeset 0da546665075aefbb476e192ed64122d340164f4 by Ned Deily in branch 'master': bpo-26317: Support OBJC and OBJCXX configure command line variables (GH-20176) https://github.com/python/cpython/commit/0da546665075aefbb476e192ed64122d340164f4 -- _

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Change by Ned Deily : -- pull_requests: +19474 pull_request: https://github.com/python/cpython/pull/20176 ___ Python tracker ___ ___

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Change by Roundup Robot : -- nosy: +python-dev nosy_count: 6.0 -> 7.0 pull_requests: +19002 pull_request: https://github.com/python/cpython/pull/19681 ___ Python tracker ___ __

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Ned Deily added the comment: Thanks, Terry. I'll look at it shortly. -- assignee: -> ned.deily nosy: -vstinner ___ Python tracker ___ ___

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Terry J. Reedy added the comment: The progress was the PR. I just fixed the merge conflicts, I believe correctly. Please test and review. -- nosy: +vstinner ___ Python tracker

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Change by STINNER Victor : -- nosy: +corona10 -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Change by STINNER Victor : -- nosy: -corona10 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Change by Dong-hee Na : -- nosy: +vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Dong-hee Na added the comment: I met this issue during I compile with gcc9 on my local mac machine. This issue should be fixed.. -- ___ Python tracker ___

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Dong-hee Na added the comment: Any progress? -- nosy: +corona10 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Jeffrey Kintscher added the comment: I submitted a pull request that fixes both the PythonLauncher build issue and the _scproxy module build issue. They are related because _scproxy is required to install PythonLauncher. -- ___ Python tracker

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Change by Jeffrey Kintscher : -- keywords: +patch pull_requests: +13216 stage: needs patch -> patch review ___ Python tracker ___ __

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Jeffrey Kintscher added the comment: I got it to build PythonLauncher using clang and everything else using gcc 8.3.0 by making a few configure script and makefile changes. Unfortunately, "make install" still fails because a python script that requires the unbuilt _scproxy module crashes. I'

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Jeffrey Kintscher added the comment: My mistake was not adding --enable-framework=${HOME}/sandbox/src/python3.7/inst to the configure script and then running make make install (I know... read the README file) gcc 8.3.0 doesn't like the Xcode system headers included by the .m files. I will

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Ned Deily added the comment: THe _scproxy.c compile error is a separate issue. The problem arises in an Apple-supplied include file and there are many reports on the web of clang vs gcc differences like this. I'm not sure what we could or should do about it other than forcing _scproxy to a

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Jeffrey Kintscher added the comment: Module/_scproxy.c compiles cleanly with clang 10.0.0 and fails with GNU gcc 8.3.0. Below is the relevant compiler error: building '_scproxy' extension gcc-8 -Wno-unused-result -Wsign-compare -g -Og -Wall -pipe -std=c99 -Wextra -Wno-unused-result -Wno-unus

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Jeffrey Kintscher added the comment: This is still an issue with the 3.7 and the master branches. The Objective-C portion of the build still fails with gcc 8.3.0 on OS X Mojave (14.x). Specifying OBJC and OBJC++ on the configure command line does nothing because there is nothing in the scrip

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Terry J. Reedy added the comment: 3.5 is and 3.6 will soon be on security fix only status. Robert, please verify that this is still an issue with 3.7 and the current build files. -- nosy: +terry.reedy versions: +Python 3.7 -Python 3.5, Python 3.6

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Changes by Terry J. Reedy : -- nosy: -terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Terry J. Reedy added the comment: When you reply by email to an email, please snip off the quote, except for possible a line that you are responding to. The disposition of this issue for 3.5+ is up to Ned or Ronald. -- ___ Python tracker

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

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 wrote: > > Terry J. Reedy added the comment: > > 3.4 only gets security fixes > > -- > nosy: +terry.reedy > stage: -> needs patch > type: -> compile error > version

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Terry J. Reedy added the comment: 3.4 only gets security fixes -- nosy: +terry.reedy stage: -> needs patch type: -> compile error versions: +Python 3.5, Python 3.6 -Python 3.4 ___ Python tracker _

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

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/automake/manu

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Ronald Oussoren 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? Make's default ruleset for compiling .m files uses $(CC) and doesn't look at $(OBJC). I wouldn't be opposed to a p

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

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, F

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

Ronald Oussoren added the comment: The build fails while building the "Python Launcher" application. This is an Objective-C project. If GCC doesn't support the system headers on OSX 10.11 there's nothing the Python project can do about that. -- nosy: +ronaldoussoren

[issue26317] Build Problem with GCC + Macintosh OS X 10.11 El Capitain

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 for C