[issue28584] ICC compiler check is too permissive

Change by Ben Boeckel : -- nosy: +mathstuf ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue28584] ICC compiler check is too permissive

Irit Katriel added the comment: Closed issue44832 as a duplicate of this. -- nosy: +iritkatriel ___ Python tracker ___ ___

[issue28584] ICC compiler check is too permissive

Change by Zachary Ware : -- versions: +Python 3.10, Python 3.11, Python 3.9 -Python 3.8 ___ Python tracker ___ ___ Python-bugs-list

[issue28584] ICC compiler check is too permissive

Change by STINNER Victor : -- nosy: +vstinner ___ Python tracker ___ ___

[issue28584] ICC compiler check is too permissive

Gianfranco added the comment: My first attempt was instead of *gcc* to just check for *gcc this avoids when "icc" is the last part of the string, I admit this is not too strong. Another approach is to use basename with cut -d " " -f 1 to pick just the first

[issue28584] ICC compiler check is too permissive

Gianfranco added the comment: I'm attaching the patch that works also for parameters, e.g. when CC contains --sysroot=/home/icc or similar. we can mark https://bugs.python.org/issue33341 duplicate to this one I think -- nosy: +locutusofborg versions:

[issue28584] ICC compiler check is too permissive

Josh Rosenberg added the comment: It's probably bad form, but I've seen people set CC to name/path to compiler followed by switches, e.g.: export CC='gcc -march=native -O3' or the like (usually because they want to keep the build tool's default CFLAGS, and setting CFLAGS causes them to be

[issue28584] ICC compiler check is too permissive

Changes by Zachary Ware : -- nosy: +zach.ware stage: -> patch review versions: -Python 3.3, Python 3.4 ___ Python tracker ___

[issue28584] ICC compiler check is too permissive

Changes by Carmelo Piccione : -- versions: +Python 2.7, Python 3.3, Python 3.4 ___ Python tracker ___

[issue28584] ICC compiler check is too permissive

New submission from Carmelo Piccione: if the ${CC} variable has an encoded path which contains "icc" anywhere in the string, it will be interpreted by the configure script as an icc compiler rather than gcc. This is due to matching on *icc* in various places. Example: