[issue44096] Bad clang detection in configure script

[Ned Deily]

Ned Deily  added the comment:

Thanks for the report. Let’s hold off on writing a patch for now until I’ve had 
a chance to investigate the multiple issues here. That should be a few days 
after some imminent PyCon events.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44096] Bad clang detection in configure script

[Ned Deily]

Change by Ned Deily :


--
assignee:  -> ned.deily
nosy: +ned.deily

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44096] Bad clang detection in configure script

[Rishav Kundu]

New submission from Rishav Kundu :

Because autoconf detects `cc` before `clang` [1], this means that most of the 
checks in configure.ac that compare $CC to `clang` don’t work. This in turn 
means that things like LTO and PGO don’t work — the appropriate compiler 
options do not get set.

I can write a patch if someone can reproduce this.

[1]: 
https://www.gnu.org/software/autoconf/manual/autoconf-2.62/html_node/C-Compiler.html

--
components: Build
messages: 393354
nosy: xrisk
priority: normal
severity: normal
status: open
title: Bad clang detection in configure script

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com