-
Notifications
You must be signed in to change notification settings - Fork 194
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
Update to chromium 116 #744
Comments
I think it makes sense to work on M116, yes. It'll have to be done, and I think it's not feasible to continue supporting clang 12. I'll keep trying to reach @kraj in the meantime. |
I'll start working on it, then! |
Short progress update: after a few patches (mostly additions to existing ones) mickledore builds now, kirkstone fails in the final linking step. |
Can you post the link failure (Kirkstone)? |
Sure, here you go:
I'll try to look into the error today. If you have any suspicions for possible causes, please let me know :) |
I don't know why, but it seems clang 14 fails to correctly generate the dunfell is currently building, but I'm optimistic it'll build as well given that it also uses clang 14. |
dunfell also builds fine, I'll get a PR ready tomorrow. |
https://chromereleases.googleblog.com/2023/08/stable-channel-update-for-desktop_15.html
Currently blocked on #741 being merged.
@rakuco do you think it makes sense to start working on this update already, given that the only thing preventing the 115 PR from being merged is that we haven't figured out yet how to integrate your
dunfell-clang14
branch intometa-clang
?The text was updated successfully, but these errors were encountered: