[issue44832] Compiler detection is not strict enough

[Irit Katriel]

Change by Irit Katriel :


--
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> ICC compiler check is too permissive

___
Python tracker 

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

[issue44832] Compiler detection is not strict enough

[Ben Boeckel]

New submission from Ben Boeckel :

Generally, the `configure.ac` script tries to detect compilers based on the 
path to the compiler. This is mostly fine, but trips up when using `mpicc` as 
the compiler. Even if the underlying compiler is `gcc`, this gets detected as 
`icc` in various situations.

The best solution is to do some compiler introspection like CMake does to 
determine what the compiler actually is, but I'm not familiar with the patterns 
used or available tools in autotools for such things.

--
components: Build
messages: 398920
nosy: mathstuf
priority: normal
severity: normal
status: open
title: Compiler detection is not strict enough
type: behavior
versions: Python 3.10, Python 3.11, Python 3.9

___
Python tracker 

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