[New-bugs-announce] [issue44093] compiler detection on macOS seems to be incorrect

Rishav Kundu report at bugs.python.org
Sun May 9 23:01:36 EDT 2021

New submission from Rishav Kundu <rishav.kundu98 at gmail.com>:

On macOS devices, the configure script seems to always detect gcc, even though Apple does not ship with gcc — the gcc binary is simply a wrapper around clang (probably llvm-gcc?)

I believe the issue is with these lines.


Concretely, gcc —-version produces this on my computer:

$ gcc --version
Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
Apple clang version 12.0.5 (clang-1205.0.22.9)
Target: x86_64-apple-darwin20.4.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

Perhaps an additional check for “clang” would solve the issue.

components: Build
messages: 393346
nosy: xrisk
priority: normal
severity: normal
status: open
title: compiler detection on macOS seems to be incorrect
type: behavior
versions: Python 3.10, Python 3.11, Python 3.6, Python 3.7, Python 3.8, Python 3.9

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list