➜

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 Robert P Fischer
Recipients Robert P Fischer, ned.deily, ronaldoussoren
Date 2016-02-12.04:45:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAC_jL3wFqoXBhq6ziKBWUizf+=U5tcMYc8o2QDrqfC7AJwZ+_A@mail.gmail.com>
In-reply-to <1455206705.88.0.63317003714.issue26317@psf.upfronthosting.co.za>
Content 
> 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/manual/html_node/Objective-C-Support.html

https://www.gnu.org/software/autoconf/manual/autoconf-2.61/html_node/Output-Variable-Index.html#Output-Variable-Index

https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=using%20objective%20c%20with%20autoconf%20automake

I wouldn't be opposed to a patch that makes it possible to specify an ObjC
> compiler, could you write such a patch?  BTW. The patch should also update
> the autoconf script (use AC_PROG_OBJC).

Sorry, I don't do Autotools --- a software package that came to us directly
from the seventh level of Hell.  CMake's main claim to fame is it's not as
bad.
History
Date User Action Args
2016-02-12 04:45:53Robert P Fischersetrecipients: + Robert P Fischer, ronaldoussoren, ned.deily
2016-02-12 04:45:53Robert P Fischerlinkissue26317 messages
2016-02-12 04:45:52Robert P Fischercreate