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

Can't build an application that using Glommio #651

Open
Eugene-Usachev opened this issue Apr 14, 2024 · 6 comments
Open

Can't build an application that using Glommio #651

Eugene-Usachev opened this issue Apr 14, 2024 · 6 comments

Comments

@Eugene-Usachev
Copy link

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
Copy link
Collaborator

glommer commented Apr 15, 2024

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
Copy link
Author

No. I just added glommio in Cargo.toml.

@vlovich
Copy link
Contributor

vlovich commented Apr 16, 2024

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
Copy link

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
Copy link

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
Copy link

installing git fixed it for me too

sudo apt install git-all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants