➜

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.

classification
Title: Compiler detection is not strict enough
Type: behavior Stage: resolved
Components: Build Versions: Python 3.11, Python 3.10, Python 3.9
process
Status: closed Resolution: duplicate
Dependencies: Superseder: ICC compiler check is too permissive
View: 28584
Assigned To: Nosy List: mathstuf
Priority: normal Keywords:

Created on 2021-08-04 17:52 by mathstuf, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Messages (1)
msg398920 - (view) Author: Ben Boeckel (mathstuf) Date: 2021-08-04 17:52 
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.
History
Date User Action Args
2022-04-11 14:59:48adminsetgithub: 88995
2022-03-19 16:05:54iritkatrielsetstatus: open -> closed
superseder: ICC compiler check is too permissive
resolution: duplicate
stage: resolved
2021-08-04 17:52:17mathstufcreate