-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
cygwin CI failure with LTO? #13465
Comments
Thanks for pinging me about this. A gcc package update was just rolled out, so i suspect that may well be involved. |
Unfortunately, this is unlikely to be resolved quickly, so I suggest you disable these tests for the moment. |
A GCC update broke this and is being investigated Bug: #13465
Disabled for now. Keeping the issue open. |
This is a weird one, and the error message is totally misleading. You fix this by installing
If it's missing, gcc is supposed to fall back to serial lto (e.g. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97524), but it seems that there's some regression in 12.x where it emits this confusing error message instead. |
Nice... (It looks like there was a fix but just never backported. Very logical...) |
Fixed in 11.0, and then it seems to have regressed again in 12.x (although that might be a cygwin specific thing, it's proved awkward for me to confirm that, one way or the other). FTR, here's a one-line reproducer.
|
For the past couple of days, cygwin CI runners fail:
@jon-turney
The text was updated successfully, but these errors were encountered: