Moving protobuf in V8 might cause `gclient sync` errors

31 views
Skip to first unread message

Michael Achenbach

unread,
Jul 30, 2024, 11:33:27 AM7/30/24
to v8-...@googlegroups.com
Hi!

tldr: If you run into a failure on `gclient sync` after https://crrev.com/c/5748472 lands, you'll need to manually delete third_party/protobuf once, before `gclient sync`.

Details:
I'll land https://crrev.com/c/5748472 soon, which moves protobuf back to the same location as in Chromium. A different protobuf version was in that same folder three months ago, but many developers might by now have removed it, since `gclient sync` suggests to remove such folders, e.g. by running `gclient sync -D`. In this case, there's no issue.

In case of syncing a very old checkout or a checkout where no dependencies were removed, some failures related to protobuf might occur during sync. A one-time manual removal of third_party/protobuf followed by `gclient sync` should fix this.

Cheers
Michael

--

Michael Achenbach | Software Engineer, V8 | Google Germany GmbH | Erika-Mann-Str. 33, 80636 München 

Registergericht und -nummer: Hamburg, HRB 86891 | Sitz der Gesellschaft: Hamburg | Geschäftsführer: Paul Manicle, Liana Sebastian 
Reply all
Reply to author
Forward
0 new messages