-
-
Notifications
You must be signed in to change notification settings - Fork 29.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"configure: error: internal configure error for the platform triplet" on macOS with Clang supporting --print-multiarch: #88231
Comments
I experienced this with Python 3.8 when building it as part of LibreOffice (see <https://git.libreoffice.org/core/+/b0a4b49a88aacfbc127965c0c6fe50a065eb3a0f%5E%21\> "external/python3: Clang 13 trunk implements --print-multiarch now", quoting from its commit message below) but from the sources it looks like it would still be an issue with the latest cpython main branch: Clang 13 trunk implements --print-multiarch now since <llvm/llvm-project@a921d2d2fb46b898794091e7410426c518a4f0cc\> "[Driver] Add -print-multiarch", which causes an issue when building with such a compiler on macOS:
as configure.ac computes PLATFORM_TRIPLET as "darwin", and instead of computing MULTIARCH as empty (as
to stderr), it now computes it as e.g. "x86_64-apple-darwin19.6.0" (or whatever -target is explicitly set to in $CC), so the check that they have equal values if they are both nonempty fails now when building against Clang 13 trunk. (This does not yet appear to be an issue with any Apple Clang version, though.) |
Python 3.8 is in security fix-only mode and does no longer updates for non-security fixes. Are Python 3.9 and 3.10 beta affected, too? |
"from the sources it looks like it would still be an issue with the latest cpython main branch", and if I check out current main branch and run |
We don't recommend nor do we test building Python for macOS with anything but the Apple-supplied compilers in either Xcode or the Command Line Tools and this hasn't been a problem with the clang versions in them so far but, if someone wants to provide a PR to avoid this, we can certainly look at applying it. |
@eliteraspberries, thanks for the reminder! |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: