Well, the name is pretty self-explanatory. I'm working on a patch right now. It my tests(I went through the file and replaced all occurrences of 'gcc' with 'clang'), everything compiled fine. I can't see an reason why it'd hurt something. -- Ryan
On 25/08/13 07:54, Ryan Gonzalez wrote:
Well, the name is pretty self-explanatory. I'm working on a patch right now. It my tests(I went through the file and replaced all occurrences of 'gcc' with 'clang'), everything compiled fine. I can't see an reason why it'd hurt something.
Are you suggesting that the maintainer of distutils should take over maintenance of clang, in order to make clang a part of distutils? Do the current maintainers of clang get a say in this? If that's not what you mean, perhaps what you mean isn't quite so self-explanatory as you think. In what sense should clang be added to distutils? gcc isn't currently part of distutils. It's an external dependency, not an internal component. -- Steven
On Sat, Aug 24, 2013 at 6:26 PM, Steven D'Aprano <steve@pearwood.info> wrote:
On 25/08/13 07:54, Ryan Gonzalez wrote:
Well, the name is pretty self-explanatory. I'm working on a patch right now. It my tests(I went through the file and replaced all occurrences of 'gcc' with 'clang'), everything compiled fine. I can't see an reason why it'd hurt something.
Are you suggesting that the maintainer of distutils should take over maintenance of clang, in order to make clang a part of distutils? Do the current maintainers of clang get a say in this?
If that's not what you mean, perhaps what you mean isn't quite so self-explanatory as you think. In what sense should clang be added to distutils? gcc isn't currently part of distutils. It's an external dependency, not an internal component.
The person is talking about the strings "gcc" and "clang"...
Sorry...I meant building Python C extensions with Clang. Steven D'Aprano <steve@pearwood.info> wrote:
On 25/08/13 07:54, Ryan Gonzalez wrote:
Well, the name is pretty self-explanatory. I'm working on a patch right now. It my tests(I went through the file and replaced all occurrences of 'gcc' with 'clang'), everything compiled fine. I can't see an reason why it'd hurt something.
Are you suggesting that the maintainer of distutils should take over maintenance of clang, in order to make clang a part of distutils? Do the current maintainers of clang get a say in this?
If that's not what you mean, perhaps what you mean isn't quite so self-explanatory as you think. In what sense should clang be added to distutils? gcc isn't currently part of distutils. It's an external dependency, not an internal component.
-- Steven _______________________________________________ Python-ideas mailing list Python-ideas@python.org http://mail.python.org/mailman/listinfo/python-ideas
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
In article <1679cbcd-5f05-434c-8a50-b65ce6898870@email.android.com>, Ryan <rymg19@gmail.com> wrote:
Sorry...I meant building Python C extensions with Clang.
I suggest you open an issue on the Python bug tracker with a diff patch of your suggested changes. But, FWIW, clang is being used today with Distutils on some platforms, at least, like OS X. On current versions of Python on Unix-y platforms, you should be able to dynamically override which compiler Distutils is looking for by using the CC and possibly the LDSHARED environment variables. -- Ned Deily, nad@acm.org
Ryan Gonzalez writes:
Well, the name is pretty self-explanatory. I'm working on a patch right now. It my tests(I went through the file and replaced all occurrences of 'gcc' with 'clang'), everything compiled fine. I can't see an reason why it'd hurt something.
Doesn't just CC=clang in the environment give you everything you want?
participants (6)
-
Brian Curtin -
Ned Deily -
Ryan -
Ryan Gonzalez
-
Stephen J. Turnbull -
Steven D'Aprano