too long lines were shrinked: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I . -I .. -I ../src/include -I ../src/lzma/include -O2 -pipe -march=native -fno-diagnostics-color -pthread -c -o main.o main.c make[2]: Leaving directory '/var/tmp/portage/app-arch/lrzip-next-0.13.1/work/lrzip-next-0.13.1/src' make[2]: Entering directory '/var/tmp/portage/app-arch/lrzip-next-0.13.1/work/lrzip-next-0.13.1/src' /bin/sh ../libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I . -I .. -I ../src/include -I ../src/lzma/include -O2 -pipe -march=native -fno-diagnostics-color -pthread -c -o stream.lo stream.c libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I . -I .. -I ../src/include -I ../src/lzma/include -O2 -pipe -march=native -fno-diagnostics-color -pthread -c stream.c -fPIC -DPIC -o .libs/stream.o stream.c: In function 'bzip3_decompress_buf': stream.c:620:16: error: too few arguments to function 'bz3_decode_block' 620 | dlen = bz3_decode_block(state, ucthread->s_buf, ucthread->c_len, ucthread->u_len); | ^~~~~~~~~~~~~~~~ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_no_multilib-20241216-084506 The attached etc.portage.tar.xz has all details. ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-14 * clang version 19.1.5 llvm-config: 19.1.5 Python 3.12.8 go version go1.23.4 linux/amd64 [1] php8.3 * Available Ruby profiles: [1] ruby32 (with Rubygems) [2] ruby33 (with Rubygems) * Available Rust versions: [1] rust-bin-1.83.0 * The following VMs are available for generation-2: HEAD of ::gentoo commit b2ae367c11b8d45df9d05cef136c46f009d41ee9 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Tue Dec 17 14:50:25 2024 +0000 2024-12-17 14:50:25 UTC emerge -qpvO =app-arch/lrzip-next-0.13.1 [ebuild N ] app-arch/lrzip-next-0.13.1 USE="largefile -asm -static-libs -year2038"
Created attachment 914248 [details] emerge-info.txt
Created attachment 914249 [details] app-arch:lrzip-next-0.13.1:20241217-160807.log
Created attachment 914250 [details] emerge-history.txt
Created attachment 914251 [details] environment
Created attachment 914252 [details] etc.clang.tar.xz
Created attachment 914253 [details] etc.portage.tar.xz
Created attachment 914254 [details] logs.tar.xz
Created attachment 914255 [details] qlist-info.txt
Created attachment 914256 [details] temp.tar.xz
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d6764c266bdb497d14fbd0373cd04b16d1d4bdf9 commit d6764c266bdb497d14fbd0373cd04b16d1d4bdf9 Author: Joshua Kinard <kumba@gentoo.org> AuthorDate: 2025-01-20 21:42:49 +0000 Commit: Joshua Kinard <kumba@gentoo.org> CommitDate: 2025-01-20 21:42:49 +0000 app-arch/lrzip-next: Add lrzip-next-0.13.2 to the tree Bug: https://bugs.gentoo.org/946587 Signed-off-by: Joshua Kinard <kumba@gentoo.org> app-arch/lrzip-next/Manifest | 2 +- .../lrzip-next/{lrzip-next-0.13.1.ebuild => lrzip-next-0.13.2.ebuild} | 2 +- app-arch/lrzip-next/lrzip-next-9999.ebuild | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-)
This should be fixed not w/ lrzip-next-0.13.2. Thanks!
