-
Notifications
You must be signed in to change notification settings - Fork 1.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
[msys2] fails to build on GCC-based environments #9245
Comments
This looks like something wrong in the environment, or more likely, something wrong in the toolchain. From what I can see, you're getting linker errors from Rust symbols. That generally shouldn't happen AIUI. But to be honest, I don't know much about the For reference, one of the functions in the linker error is this one. And the only way that function isn't defined is if One thing that catches my eye is that the target seems to be 64-bit, but it also has a "32" in the name via The |
|
Yeah I dunno. I'm also the maintainer of |
There are no hacks involved, x86_64-w64-mingw32 is GNU name for this target and x86_64-pc-windows-gnu is LLVM name (inherited by Rust) but they mean the same thing. Looking at the logs it looks like the statics might incorrectly imported/exported or the link order is wrong but that shouldn't be caused by these crates. It's likely an issue with rustc but I won't have time to debug it soon. |
I haven't tested ruff 0.1.11 yet and also didn't try to rebuild with rust 1.75.0. I can do this only on January 8th |
I have tested current git repo with 1.74 and 1.75, they both have the same issue. |
It has "regressed" in 3ce145c and changing |
thanks for investigation! |
we fixed the issue. can be closed |
I ran into this exact error while trying to add Since per-target profiles aren't really a thing, I was able to get around this issue by setting the environment variable |
build script for version 0.1.9 (package ruff_cli) fails with
see PR actions for full log
on GCC-based environments (MINGW64 and UCRT64). clang-based environment (CLANG64) work fine
The text was updated successfully, but these errors were encountered: