-
-
Notifications
You must be signed in to change notification settings - Fork 173
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
Build failure with gcc13 #573
Comments
Hey! These are warnings, not errors. I'll fix, but it shouldn't block anyone from using et as-is. |
The build fail was actually in the sentry 3rd party thing. We use https://build.opensuse.org/package/view_file/openSUSE:Factory/EternalTerminal/ET-gcc13.patch?expand=1 now. |
Is it fixed in the latest version of sentry?
…On Tue, Jun 27, 2023, 8:43 AM Michael Vetter ***@***.***> wrote:
The build fail was actually in the sentry 3rd party thing. We use
https://build.opensuse.org/package/view_file/openSUSE:Factory/EternalTerminal/ET-gcc13.patch?expand=1
now.
—
Reply to this email directly, view it on GitHub
<#573 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACK5P7WDFQTGNHWUKTT7ADXNLPP7ANCNFSM6AAAAAAWNDTUR4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
It's fixed with getsentry/breakpad@7ea7ded |
@jubalh can you confirm that latest master branch builds on gcc 13? 13 isn't part of github actions yet so I can't test in CI... |
I don't know about the master branch but we build 6.2.4 with this patch succesfully with gcc in openSUSE. |
Full log
The text was updated successfully, but these errors were encountered: