Python build fails if the path to the compiler includes strings common with the compiler names (icc, gcc, etc)

[jmicco]

Bug report

Checklist

• I am confident this is a bug in CPython, not a bug in a third-party project
• I have searched the CPython issue tracker,
  and am confident this bug has not been reported before

CPython versions tested on:

3.11

Operating systems tested on:

Linux

Output from running 'python -VV' on the command line:

|Python 3.11.4 (main, Jun 6 2023, 22:16:46) [GCC 12.2.0]

A clear and concise description of the bug:

My home directory includes the string "icc" because that is my userid (jmicco).

When using GCC installed into my home directory, incorrect options were passed to the compiler that were invalid because the code uses icc to determine when to add the flags. This causes the build to fail immediately with an illegal compiler option for GCC:

case "$CC" in
*mpicc*)
    CFLAGS_NODIST="$CFLAGS_NODIST"
    ;;
*icc*)
    # ICC needs -fp-model strict or floats behave badly
    CFLAGS_NODIST="$CFLAGS_NODIST -fp-model strict"
    ;;
*xlc*)
    CFLAGS_NODIST="$CFLAGS_NODIST -qalias=noansi -qmaxmem=-1"
    ;;
esac

The -fp-model strict option was passed to GCC when running the compiler from my sandbox - this caused the build to completely fail

Linked PRs

• gh-108465: Use compiler basename when determining compiler flags #108392