-
Notifications
You must be signed in to change notification settings - Fork 6
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
mswin
builds started failing due to libclang differences
#27
Comments
Interesting. The last passing CI was using the Windows-2022 20221027.1 image, the first failing job was using 20221120.1. That info is in the 'Set up job' step, within the 'Runner Image' group. Rust changed from 1.64.0 to 1.65.0, and Visual Studio was also updated. I don't believe there have been related changes to the repo that creates the vcpkg packages, this repo, or setup-ruby. I did change the build scripts for mswin in ruby-loco, but I don't think there were any changes that affect the build, it was more to align the three builds (mingw, ucrt, & mswin) and allow them to share test scripts. Re I don't think I've tried to run rb-sys CI locally. I wonder if a 3.1.x Ruby mswin build passes... |
So it seems like msys2 may have updated clang, and now windows builds for rust are breaking. I've managed to downgrade to clang-14, but am stuck because ruby cannot find |
Let me check tomorrow. What happens if you install |
Same issue. GHA runner has clang 15 installed by default so we shouldn't need it. What surprised me is rubygems CI builds seem to be working... Although I'm not 100% sure. |
They bypassed/skipped the Rust extension tests when this happened... I did the same in ruby-loco. |
Problem
Builds that were previously working on rb-sys are now failing. The builds were working as of 2022-11-18, and as of today (11-30-2022) they are failing.
It seems like a libclang resolution issue. The error I get looks like:
At one point, I had to configure the
LIBCLANG_PATH
withgcm
to make things work. But this code has been disabled for awhile now and things worked properly. Maybe I should try adding this back?I'm wondering if any you know of any recent changes in the mswin Ruby image that may be causing this? Otherwise, this may be a github actions runner thing. Thanks in advance! ❤️
The text was updated successfully, but these errors were encountered: