Closed ddelnano closed 2 years ago
@tavplubix appreciate your help so far in #42110. I've created this separate issue so we can discuss this in more detail here.
There is something wrong with Vagrant. Build it without Vagrant.
I have no idea why Vagrant does not work. I don't use Vagrant.
I also have heard that Vagrant is not fashionable anymore, so I'm feeling ok with the fact I missed it. You can create an issue in their repository.
If you are an expert, you can debug this problem on your own.
Check how exactly the protoc
file was generated and what is wrong with this process.
Look inside the file in a hex editor.
My
git status
only shows that theVagrantfile
and.vagrant
directories have been created. Otherwise my repo is clean on master (eb637a6f81c4908e9e5ed72776b4edbc88f263da)Operating system
Cmake version 3.22.1
Ninja version 1.10.1
Compiler name and version Clang 15.0.3
Full cmake and/or ninja output
This comment also has more details on the debugging I've done. It appears
protoc
is built for the wrong architecture even though it seems clang is receiving the correct arguments to compile the binary for x86_64.