-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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 upb to fix compilation error with gcc 10 #12077
Conversation
@vbatts Can you verify if this PR fix the compilation error for you? |
0b0dc95
to
de481e7
Compare
The change looks fine, but the distfile tests are still failing in various ways. |
It seems to be downloading 9effcbcb27f0a665f9f345030188c0b291e32482 instead of the newer version. |
de481e7
to
33e8795
Compare
@aiuto Nice catch, fixed! |
Last time I tried to update a dependency I had similar pain. I finally filed bug #12081 about it. |
33e8795
to
58a98cf
Compare
Hmm, looks like we have to explicitly override upb in the WORKSPACE file. |
Now it fails in the non_determinism test. Could it be related to //third_party/grpc:grpc_1.26.0.patch? |
Or maybe it is the grpc patch doing it.
…On Thu, Sep 10, 2020 at 10:24 AM Yun Peng ***@***.***> wrote:
Hmm, looks like we have to explicitly override the upb on WORKSPACE file.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12077 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXHHHE3R34VWC43HYSA7NDSFDOSVANCNFSM4RERROXQ>
.
|
No, the patch is for something else. The upb is actually introduced in grpc_deps(), I tried to override it by declaring it directly in Bazel's WORKSPACE file. But it doesn't seem to work because the new upb version doesn't work with the old grpc version.. This is not looking good ... |
Yeah. I still see the same error with the update patch. But, if you decide you want it.
|
Thanks for coming up with the patch, unfortunately the newer version isn't compatible with grpc. The best I can come up with is to patch the original upb version, see #12083 |
So, is this PR moot, and we should do 3.5.1 with a cherrpick of #12083? |
Yes, looks like a regression we should fix. |
Fixes bazelbuild#12056 This is a replacement of bazelbuild#12077 after an unsuccessful attempt to upgrade upb version. Closes bazelbuild#12083. PiperOrigin-RevId: 331145667
Fixes bazelbuild#12056 This is a replacement of bazelbuild#12077 after an unsuccessful attempt to upgrade upb version. Closes bazelbuild#12083. PiperOrigin-RevId: 331145667
Fixes #12056