You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also, you must have protoc version 3.12.0 or later (https://github.com/protocolbuffers/protobuf/releases/tag/v3.12.0). This is needed for the --experimental_allow_proto3_optional option that is used. If using ubuntu, version 22.04 or later is required to have a new enough protobuf-compiler package to meet this requirement.
Another issue I had was that cargo build makes an executable tied to certain versions of GLIBC. If the system you want to run on is an older system (such as ubuntu 20.04) that has an older version of GLIBC than you compile with, it won't work if it is too old. The fix for that is to run
which makes a binary file that is truly statically linked and does not rely on GLIBC. The output goes in the subdirectory target/x86_64-unknown-linux-gnu/release. There are also some build files placed in the target/release subdirectory, but there is no final binary file. So, I'm not sure why there are extra build files placed there instead of everything being generated under target/x86_64-unknown-linux-gnu/release.
The following step is missing from the installation instructions to fetch build dependencies:
Also, you must have
protoc
version 3.12.0 or later (https://github.com/protocolbuffers/protobuf/releases/tag/v3.12.0). This is needed for the--experimental_allow_proto3_optional
option that is used. If using ubuntu, version 22.04 or later is required to have a new enoughprotobuf-compiler
package to meet this requirement.Another issue I had was that
cargo build
makes an executable tied to certain versions of GLIBC. If the system you want to run on is an older system (such as ubuntu 20.04) that has an older version of GLIBC than you compile with, it won't work if it is too old. The fix for that is to runwhich makes a binary file that is truly statically linked and does not rely on GLIBC. The output goes in the subdirectory
target/x86_64-unknown-linux-gnu/release
. There are also some build files placed in thetarget/release
subdirectory, but there is no final binary file. So, I'm not sure why there are extra build files placed there instead of everything being generated undertarget/x86_64-unknown-linux-gnu/release
.See also:
.cargo/config.toml
so it doesn't need to be passed on the command line.The text was updated successfully, but these errors were encountered: