-
Notifications
You must be signed in to change notification settings - Fork 103
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
Compiling the project fails, following instructions from readme. #168
Comments
marin-m
added a commit
that referenced
this issue
Sep 29, 2024
Options: -h, --help Display this message --cfg SPEC Configure the compilation environment. SPEC supports the syntax `NAME[="VALUE"]`. --check-cfg SPEC Provide list of expected cfgs for checking -L [KIND=]PATH Add a directory to the library search path. The optional KIND can be one of dependency, crate, native, framework, or all (the default). -l [KIND[:MODIFIERS]=]NAME[:RENAME] Link the generated crate(s) to the specified native library NAME. The optional KIND can be one of static, framework, or dylib (the default). Optional comma separated MODIFIERS (bundle|verbatim|whole-archive|as-needed) may be specified each with a prefix of either '+' to enable or '-' to disable. --crate-type [bin|lib|rlib|dylib|cdylib|staticlib|proc-macro] Comma separated list of types of crates for the compiler to emit --crate-name NAME Specify the name of the crate being built --edition 2015|2018|2021|2024 Specify which edition of the compiler to use when compiling code. The default is 2015 and the latest stable edition is 2021. --emit [asm|llvm-bc|llvm-ir|obj|metadata|link|dep-info|mir] Comma separated list of types of output for the compiler to emit --print [crate-name|file-names|sysroot|target-libdir|cfg|check-cfg|calling-conventions|target-list|target-cpus|target-features|relocation-models|code-models|tls-models|target-spec-json|all-target-specs-json|native-static-libs|stack-protector-strategies|link-args|deployment-target] Compiler information to print on stdout -g Equivalent to -C debuginfo=2 -O Equivalent to -C opt-level=2 -o FILENAME Write output to <filename> --out-dir DIR Write output to compiler-chosen filename in <dir> --explain OPT Provide a detailed explanation of an error message --test Build a test harness --target TARGET Target triple for which the code is compiled -A, --allow LINT Set lint allowed -W, --warn LINT Set lint warnings --force-warn LINT Set lint force-warn -D, --deny LINT Set lint denied -F, --forbid LINT Set lint forbidden --cap-lints LEVEL Set the most restrictive lint level. More restrictive lints are capped at this level -C, --codegen OPT[=VALUE] Set a codegen option -V, --version Print version info and exit -v, --verbose Use verbose output Additional help: -C help Print codegen options -W help Print 'lint' options and default settings -Z help Print unstable compiler options --help -v Print the full set of options rustc accepts version in the root README.md (issue #168)
Hello, Thank you for noticing, anyway the The dead code warning has been fixed at the moment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to build songrec v0.4.2 on antiX 23.1 full runit 64 bit, kernel 6.5.0-0.deb12.4-amd64-smp, packages build-essential libasound2-dev libpulse-dev libgtk-3-dev libssl-dev installed.
How to make it build properly? Seems there is some functionality missing and the resulting executable has 8,7 MiB compared with the cargo install in home folder, which has 9,2 MiB size.
Additional note: You should possibly update your readme file:
None of this works.
songrec v0.4.2 needs rustc 1.65 or higher, while debian stable installs 1.63 only. So also the statement about min version 1.43 is obviously wrong.
I had to use rustup
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
on bookworm instead of apt install.This installs currently rustc 1.78.0 and cargo 1.78.0 which compiles at least the homefolder method without any error messages.
The text was updated successfully, but these errors were encountered: