We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
boost/preprocessor/stringize.hpp
I added the crate to my project and I get the following error when I try to build it:
The following warnings were emitted during compilation: warning: In file included from src/vendor/chacha.c:15: warning: src/vendor/warnings.h:14:10: fatal error: boost/preprocessor/stringize.hpp: No such file or directory warning: 14 | #include <boost/preprocessor/stringize.hpp> warning: | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ warning: compilation terminated. error: failed to run custom build command for `cryptonight-rs v0.2.1` Caused by: process didn't exit successfully: `<project-path>/target/debug/build/cryptonight-rs-5a31b906614e066a/build-script-build` (exit status: 1) --- stdout TARGET = Some("x86_64-unknown-linux-gnu") OPT_LEVEL = Some("0") HOST = Some("x86_64-unknown-linux-gnu") cargo:rerun-if-env-changed=CC_x86_64-unknown-linux-gnu CC_x86_64-unknown-linux-gnu = None cargo:rerun-if-env-changed=CC_x86_64_unknown_linux_gnu CC_x86_64_unknown_linux_gnu = None cargo:rerun-if-env-changed=HOST_CC HOST_CC = None cargo:rerun-if-env-changed=CC CC = None cargo:rerun-if-env-changed=CFLAGS_x86_64-unknown-linux-gnu CFLAGS_x86_64-unknown-linux-gnu = None cargo:rerun-if-env-changed=CFLAGS_x86_64_unknown_linux_gnu CFLAGS_x86_64_unknown_linux_gnu = None cargo:rerun-if-env-changed=HOST_CFLAGS HOST_CFLAGS = None cargo:rerun-if-env-changed=CFLAGS CFLAGS = None cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS CRATE_CC_NO_DEFAULTS = None DEBUG = Some("true") CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2") running: "cc" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-gdwarf-4" "-fno-omit-frame-pointer" "-m64" "-I" "src/vendor/crypto" "-I" "src/vendor/common" "-Wall" "-Wextra" "-maes" "-Ofast" "-fexceptions" "-o" "<project-path>/target/debug/build/cryptonight-rs-b48f7523b049627f/out/src/vendor/aesb.o" "-c" "src/vendor/aesb.c" exit status: 0 running: "cc" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-gdwarf-4" "-fno-omit-frame-pointer" "-m64" "-I" "src/vendor/crypto" "-I" "src/vendor/common" "-Wall" "-Wextra" "-maes" "-Ofast" "-fexceptions" "-o" "<project-path>/target/debug/build/cryptonight-rs-b48f7523b049627f/out/src/vendor/blake256.o" "-c" "src/vendor/blake256.c" exit status: 0 running: "cc" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-gdwarf-4" "-fno-omit-frame-pointer" "-m64" "-I" "src/vendor/crypto" "-I" "src/vendor/common" "-Wall" "-Wextra" "-maes" "-Ofast" "-fexceptions" "-o" "<project-path>/target/debug/build/cryptonight-rs-b48f7523b049627f/out/src/vendor/chacha.o" "-c" "src/vendor/chacha.c" cargo:warning=In file included from src/vendor/chacha.c:15: cargo:warning=src/vendor/warnings.h:14:10: fatal error: boost/preprocessor/stringize.hpp: No such file or directory cargo:warning= 14 | #include <boost/preprocessor/stringize.hpp> cargo:warning= | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ cargo:warning=compilation terminated. exit status: 1 --- stderr error occurred: Command "cc" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-gdwarf-4" "-fno-omit-frame-pointer" "-m64" "-I" "src/vendor/crypto" "-I" "src/vendor/common" "-Wall" "-Wextra" "-maes" "-Ofast" "-fexceptions" "-o" "<project-path>/target/debug/build/cryptonight-rs-b48f7523b049627f/out/src/vendor/chacha.o" "-c" "src/vendor/chacha.c" with args "cc" did not execute successfully (status code exit status: 1).
Note that I replaced the actual project path with <project-path> for privacy reasons.
<project-path>
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I added the crate to my project and I get the following error when I try to build it:
The text was updated successfully, but these errors were encountered: