DataDog / glommio

Glommio is a thread-per-core crate that makes writing highly parallel asynchronous applications in a thread-per-core architecture easier for rustaceans.
Other
3.12k stars 164 forks source link

Can't build an application that using Glommio #651

Open Eugene-Usachev opened 7 months ago

Eugene-Usachev commented 7 months ago

When I try to build my application I always get error message with text:

error: failed to run custom build command for glommio v0.9.0

Caused by: process didn't exit successfully: /app/target/release/build/glommio-03f2d8ce6c58b621/build-script-build (exit status: 101) --- stderr thread 'main' panicked at /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/glommio-0.9.0/build.rs:18:18: called Result::unwrap() on an Err value: Os { code: 2, kind: NotFound, message: "No such file or directory" } note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

I tried to build it in Docker and got the same error.

glommer commented 7 months ago

this is the liburing build dir. Are you using git, or got the tarball from somewhere?

If you are using git, the git submodule command should do. If not, you will have to get the liburing source yourself.

Eugene-Usachev commented 7 months ago

No. I just added glommio in Cargo.toml.

vlovich commented 7 months ago

That /usr/local/ location of the cargo registry is super weird. Isn't that usually in the home directory? I suspect the problem is something weird within your Docker.

One workaround (if you are stuck on fixing) might be to clone liburing manually and point to it via the GLOMMIO_LIBURING_DIR environment variable to bypass the submodule logic in build.rs.

emschwartz commented 3 months ago

I ran into this issue on a Debian 12 instance and it turned out the problem was that git wasn't installed so the git submodule command failed. @Eugene-Usachev can you double-check that git is available?

schalk-b commented 3 months ago

I ran into this issue on a Debian 12 instance and it turned out the problem was that git wasn't installed so the git submodule command failed. @Eugene-Usachev can you double-check that git is available?

I had the same issue. This fixed it for me.

robert-king commented 2 months ago

installing git fixed it for me too

sudo apt install git-all