You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
compiler detection on macOS seems to be incorrect #88259
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?)
The issue seems to be solved. We can close the issue.
Perhaps I don't understand the desired result but it doesn't look solved to me. In particular, the test:
if test -n "`"$found_gcc" --version | grep llvm-gcc`"
fails because compilers provided by current versions of Apple's Xcode or Command Line Tools no longer include the string llvm-gcc in their reported versions:
$ gcc --version
Apple clang version 14.0.3 (clang-1403.0.22.14.1)
Target: x86_64-apple-darwin22.4.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
Activity
xrisk commentedon May 10, 2021
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.
cpython/configure.ac
Lines 630 to 635 in 8e8307d
Concretely, gcc —-version produces this on my computer:
Perhaps an additional check for “clang” would solve the issue.
furkanonder commentedon May 9, 2023
@ned-deily The issue seems to be solved. We can close the issue.
ned-deily commentedon May 9, 2023
Perhaps I don't understand the desired result but it doesn't look solved to me. In particular, the test:
fails because compilers provided by current versions of Apple's Xcode or Command Line Tools no longer include the string
llvm-gccin their reported versions:erlend-aasland commentedon Apr 12, 2024
Superseded by #110577.
Let's continue the discussion over there.
See also: