-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Meson fails to detect linker with llvm/clang #13894
Comments
I am encountering the same problem when trying to use meson via The final error line is
I have the same meson version: 1.6.0, I also have meson-python 0.17.1, vc14-runtime, and vs2015_runtime installed in the build environment. Edit: On a double check, |
@subhacom What makes you think your problem is related to this issue? The error message you report does not say anything about what made the wheel building fail. Please enable verbose logging in pip and report the relevant part of the build log. |
@dnicolodi I actually got the exact same error earlier (though I only mentioned the final line): |
Seemingly unrelated, however the In this issue we tackle some of the possible fixes, in the midst of it all there is a suggestion of launching VSCode from a In the same vein I tried launching It's worth pointing out that I also got meson to recognize |
Describe the bug
Running
meson setup build
in a correctly set up project fails due to the linker being missing.Linker's not missing though, but meson thinks it is. Before upgrading python and meson this wasn't causing any issues, however I don't remember the exact versions for either.
Error thats shown in the command line after executing
meson setup build
The log meson is referring to:
meson-logs\meson-log.txt
To Reproduce
Here's the
meson.build
fileExpected behavior
I expected the linker to be found, since it's in the same directory as the compiler executable and
clang
is properly setup.system parameters
This is not a cross compiled build.
Windows 10 1809
python 3.12.6
meson 1.6.0
clang 18.1.0rc
The text was updated successfully, but these errors were encountered: