➜

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 Jeffrey.Kintscher
Recipients Jeffrey.Kintscher, Robert P Fischer, ned.deily, ronaldoussoren, terry.reedy
Date 2019-05-10.21:53:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1557525183.27.0.991629171808.issue26317@roundup.psfhosted.org>
In-reply-to
Content 
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 dig into this now that I am using the proper build steps.

As a side note, I find it counter-intuitive that Mac/Makefile only gets invoked by 'make install' to build the Objective-C source files. IMHO they should be built by "make" and then installed by "make install". Forcing a build and install in one step can be dangerous and accidentally leave the system in an undesirable state when the build process fails with a partial install. Also, --enable-framework should use a subpath of --prefix by default for the framework installation instead of defaulting to /Library/Frameworks regardless of the --prefix setting.
History
Date User Action Args
2019-05-10 21:53:03Jeffrey.Kintschersetrecipients: + Jeffrey.Kintscher, terry.reedy, ronaldoussoren, ned.deily, Robert P Fischer
2019-05-10 21:53:03Jeffrey.Kintschersetmessageid: <1557525183.27.0.991629171808.issue26317@roundup.psfhosted.org>
2019-05-10 21:53:03Jeffrey.Kintscherlinkissue26317 messages
2019-05-10 21:53:03Jeffrey.Kintschercreate