-
Notifications
You must be signed in to change notification settings - Fork 648
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
librespot fails to build on FreeBSD after recent update to 0.6 #1393
Comments
Hello, so apparently after updating the port to the newest edition, it doesn't quite build. Could you help troubleshoot? |
There are existing (closed) issues relating to these sorts of build problems. Please check those don't solve your issue. |
#1382 is the issue that solves the problem for good. Not closed yet. |
Great point. You could wait for that, if you like. Or solve it now by satisfying the current dependencies. It's also at https://github.com/librespot-org/librespot/wiki/Compiling#linuxmacoswindows if your search for the recent issues is somehow fruitless. |
Any news from this? I was still unable to build the current release on FreeBSD...
Am 16. November 2024 um 23:49 schrieb "Roderick van Domburg" ***@***.*** ***@***.***?to=%22Roderick%20van%20Domburg%22%20%3Cnotifications%40github.com%3E >:
…
Closed #1393 #1393 as completed.
—
Reply to this email directly, view it on GitHub #1393 (comment) , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACDLR2HZESPRF3EXOBNN75L2A7DZLAVCNFSM6AAAAABRPFOKU2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGMZDEOBZHE3DMMI .
You are receiving this because you are subscribed to this thread.
|
Can you clarify, are still unable to build even after fixing the build environment to satisfy the new dependencies? |
tried the ports-version this morning and failed with the warning / error below on FreeBSD 13.4-RELEASE
Same error on building the git-checkout with "cargo build --release --no-default-features"
As recomended in the librespot/COMPILING.md i installed the build-essentials, upgraded gcc to 13.3
[code]
--- stdout
cargo:rerun-if-env-changed=AWS_LC_SYS_NO_PREFIX
cargo:rerun-if-env-changed=AWS_LC_SYS_PREGENERATING_BINDINGS
cargo:rerun-if-env-changed=AWS_LC_SYS_EXTERNAL_BINDGEN
cargo:rerun-if-env-changed=AWS_LC_SYS_NO_ASM
cargo:rerun-if-env-changed=AWS_LC_SYS_CFLAGS
cargo:rerun-if-env-changed=AWS_LC_SYS_PREBUILT_NASM
cargo:rerun-if-env-changed=AWS_LC_SYS_C_STD
cargo:rerun-if-env-changed=AWS_LC_SYS_CMAKE_BUILDER
cargo:rerun-if-env-changed=AWS_LC_SYS_STATIC
cargo:rerun-if-env-changed=CMAKE
cargo:warning=Building with: CMake
cargo:warning=Symbol Prefix: Some("aws_lc_0_22_0")
cargo:rerun-if-env-changed=CMAKE
cargo:warning=CMAKE environment variable set: cmake
cargo:warning=Generating bindings - external bindgen. Platform: x86_64-unknown-freebsd
--- stderr
Consider installing the bindgen-cli: `cargo install --force --locked bindgen-cli`
See our User Guide for more information about bindgen:https://aws.github.io/aws-lc-rs/index.html
Failure invoking external bindgen! External bindgen command failed.
thread 'main' panicked at /usr/ports/multimedia/librespot/work/librespot-0.6.0/cargo-crates/aws-lc-sys-0.22.0/builder/main.rs:566:5:
aws-lc-sys build failed. Please enable the 'bindgen' feature on aws-lc-rs or aws-lc-sys.For more information, see the aws-lc-rs User Guide: https://aws.github.io/aws-lc-rs/index.html
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
*** Error code 101
[/code]
Am 21. November 2024 um 11:51 schrieb "Nick Steel" ***@***.*** ***@***.***?to=%22Nick%20Steel%22%20%3Cnotifications%40github.com%3E >:
…
Can you clarify, are still unable to build even after fixing the build environment to satisfy the new dependencies?
—
Reply to this email directly, view it on GitHub #1393 (comment) , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACDLR2EZW5YBG2WO4TEKZCD2BW3LNAVCNFSM6AAAAABRPFOKU2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJQG44DEMBYGY .
You are receiving this because you commented.
|
|
https://pkg-status.freebsd.org/beefy22/data/141amd64-default/203aa1081a24/logs/librespot-0.6.0_1.log
The text was updated successfully, but these errors were encountered: