Skip to content
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

Bug: missing steps from installation instructions #182

Open
AndySchroder opened this issue Oct 3, 2024 · 0 comments
Open

Bug: missing steps from installation instructions #182

AndySchroder opened this issue Oct 3, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@AndySchroder
Copy link

AndySchroder commented Oct 3, 2024

The following step is missing from the installation instructions to fetch build dependencies:

apt update
apt install -y cargo protobuf-compiler build-essential

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

RUSTFLAGS="-C target-feature=+crt-static" cargo build --release --target x86_64-unknown-linux-gnu

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.

See also:

@AndySchroder AndySchroder added the bug Something isn't working label Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant