[GH-ISSUE #664] asciinema has a build error with rustls under buildroot #954

New issue

Closed

opened 2026-03-15 11:06:41 +03:00 by kerem · 1 comment

kerem commented

2026-03-15 11:06:41 +03:00

Owner

Originally created by @darcyg on GitHub (Nov 28, 2024).
Original GitHub issue: https://github.com/asciinema/asciinema/issues/664

Describe the bug
asciinema has a build error with rustls under buildroot.
In a privately customized buildroot, the asciinema package was added.
The aarch64 version builds without any issues, but the x64 version reports gcc errors.
After researching, it was confirmed that rustls, which is a dependency for building, requires the aws-lc-rs's aws-lc-sys to be upgraded to at least version 0.21.2.
Since I am not very familiar with Rust's build and package management rules, cargo.
Modifying the Cargo.toml (patch.crates-io) also failed to complete the compilation.
I hope the official team can upgrade the dependency libraries.

To Reproduce
Steps to reproduce the behavior:

make build-pkg SPKG=asciinema
error message
` CC = Some(/works/mf-haos/haos/output_x86_64/host/bin/x86_64-buildroot-linux-gnu-gcc)
RUSTC_WRAPPER = None
cargo:rerun-if-env-changed=CC_ENABLE_DEBUG_OUTPUT
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some(false)
CARGO_CFG_TARGET_FEATURE = Some(fxsr,sse,sse2)
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 = Some(-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g0 -D_FORTIFY_SOURCE=1)
cargo:rerun-if-env-changed=CC_SHELL_ESCAPED_FLAGS
CC_SHELL_ESCAPED_FLAGS = None

--- stderr
thread 'main' panicked at /works/mf-haos/haos/output_x86_64/build/asciinema-7a1a7d510a3a7a10a4b85c5cf74ec0e1e5e4a9bc/VENDOR/aws-lc-sys/builder/cc_builder.rs:271:13:

COMPILER BUG DETECTED

Your compiler (/works/mf-haos/haos/output_x86_64/host/bin/x86_64-buildroot-linux-gnu-gcc) is not supported due to a memcmp related bug reported in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189. We strongly recommend against using this compiler.
EXECUTED: true
ERROR:
OUTPUT:

note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
make[1]: *** [package/pkg-generic.mk:283: /works/mf-haos/haos/output_x86_64/build/asciinema-7a1a7d510a3a7a10a4b85c5cf74ec0e1e5e4a9bc/.stamp_built] Error 101
make[1]: Leaving directory '/works/mf-haos/haos/buildroot'
make: *** [Makefile:183: build-pkg] Error 2
`

Versions:

OS: debian 11 x64
asciinema cli: [7a1a7d510a]

Additional context
Solution Information

https://github.com/librespot-org/librespot/issues/1380
https://github.com/librespot-org/librespot/issues/1346
https://github.com/librespot-org/librespot/issues/1346
https://github.com/aws/aws-lc-rs/pull/520

Originally created by @darcyg on GitHub (Nov 28, 2024). Original GitHub issue: https://github.com/asciinema/asciinema/issues/664 **Describe the bug** asciinema has a build error with rustls under buildroot. In a privately customized buildroot, the asciinema package was added. The aarch64 version builds without any issues, but the x64 version reports gcc errors. After researching, it was confirmed that rustls, which is a dependency for building, requires the aws-lc-rs's aws-lc-sys to be upgraded to at least version 0.21.2. Since I am not very familiar with Rust's build and package management rules, cargo. Modifying the Cargo.toml (patch.crates-io) also failed to complete the compilation. I hope the official team can upgrade the dependency libraries. **To Reproduce** Steps to reproduce the behavior: make build-pkg SPKG=asciinema error message ` CC = Some(/works/mf-haos/haos/output_x86_64/host/bin/x86_64-buildroot-linux-gnu-gcc) RUSTC_WRAPPER = None cargo:rerun-if-env-changed=CC_ENABLE_DEBUG_OUTPUT cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS CRATE_CC_NO_DEFAULTS = None DEBUG = Some(false) CARGO_CFG_TARGET_FEATURE = Some(fxsr,sse,sse2) 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 = Some(-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g0 -D_FORTIFY_SOURCE=1) cargo:rerun-if-env-changed=CC_SHELL_ESCAPED_FLAGS CC_SHELL_ESCAPED_FLAGS = None --- stderr thread 'main' panicked at /works/mf-haos/haos/output_x86_64/build/asciinema-7a1a7d510a3a7a10a4b85c5cf74ec0e1e5e4a9bc/VENDOR/aws-lc-sys/builder/cc_builder.rs:271:13: ### COMPILER BUG DETECTED ### Your compiler (/works/mf-haos/haos/output_x86_64/host/bin/x86_64-buildroot-linux-gnu-gcc) is not supported due to a memcmp related bug reported in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189. We strongly recommend against using this compiler. EXECUTED: true ERROR: OUTPUT: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace warning: build failed, waiting for other jobs to finish... make[1]: *** [package/pkg-generic.mk:283: /works/mf-haos/haos/output_x86_64/build/asciinema-7a1a7d510a3a7a10a4b85c5cf74ec0e1e5e4a9bc/.stamp_built] Error 101 make[1]: Leaving directory '/works/mf-haos/haos/buildroot' make: *** [Makefile:183: build-pkg] Error 2 ` **Versions:** - OS: debian 11 x64 - asciinema cli: [7a1a7d510a3a7a10a4b85c5cf74ec0e1e5e4a9bc] **Additional context** Solution Information https://github.com/librespot-org/librespot/issues/1380 https://github.com/librespot-org/librespot/issues/1346 https://github.com/librespot-org/librespot/issues/1346 https://github.com/aws/aws-lc-rs/pull/520

kerem closed this issue

2026-03-15 11:06:46 +03:00

kerem commented

2026-03-15 11:06:52 +03:00

Author

Owner

@ku1ik commented on GitHub (May 29, 2025):

We now use aws-lc-sys 0.28 - github.com/asciinema/asciinema@136f0f4b20/Cargo.lock (L159-L161)

Can you try building the latest version?

@ku1ik commented on GitHub (May 29, 2025): We now use aws-lc-sys 0.28 - https://github.com/asciinema/asciinema/blob/136f0f4b20769f7f2d64fe4dd306bdef5003c907/Cargo.lock#L159-L161 Can you try building the latest version?