too long lines were shrinked: make[2]: Leaving directory '/var/tmp/portage/net-libs/pjproject-2.15.1/work/pjproject-2.15.1/pjlib/build' make[2]: Entering directory '/var/tmp/portage/net-libs/pjproject-2.15.1/work/pjproject-2.15.1/pjlib/build' if test ! -d ../bin; then mkdir -p ../bin; fi x86_64-pc-linux-gnu-g++ -o ../bin/pjlib-test-x86_64-pc-linux-gnu \ output/pjlib-test-x86_64-pc-linux-gnu/main.o output/pjlib-test-x86_64-pc-linux-gnu/activesock.o output/pjlib-test-x86_64-pc-linux-gnu/atomic.o output/pjlib-test-x86_64-pc-linux-gnu/echo_clt.o output/pjlib-test-x86_64-pc-linux-gnu/errno.o output/pjlib-test-x86_64-pc-linux-gnu/exception.o o /usr/lib/gcc/x86_64-pc-linux-gnu/14/../../../../x86_64-pc-linux-gnu/bin/ld: output/pjlib-test-x86_64-pc-linux-gnu/fifobuf.o: in function `fifobuf_rolling_test': fifobuf.c:(.text+0x64): undefined reference to `pj_fifobuf_capacity' /usr/lib/gcc/x86_64-pc-linux-gnu/14/../../../../x86_64-pc-linux-gnu/bin/ld: fifobuf.c:(.text+0x77): undefined reference to `pj_fifobuf_available_size' /usr/lib/gcc/x86_64-pc-linux-gnu/14/../../../../x86_64-pc-linux-gnu/bin/ld: fifobuf.c:(.text+0x1e4): undefined reference to `pj_fifobuf_capacity' ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_desktop_gnome-20250115-060502 UNMASKED: Requested by sam >=media-video/ffmpeg-7.0 >=app-text/dvisvgm-2024 >=app-text/ps2pkm-1.8_p20240311 >=app-text/texlive-2024 >=app-text/texlive-core-2024 >=dev-libs/kpathsea-6.4.0 >=dev-libs/ptexenc-1.4.6 dev-python/latexrestricted >=dev-tex/biber-2.20 >=dev-tex/biblatex-3.20 >=dev-tex/bibtexu-3.72_p20240311 >=dev-tex/glossaries-4.55 dev-tex/latex2pydata >=dev-tex/latexmk-4.85 >=dev-tex/minted-3.4.0 >=dev-tex/tex4ht-20240311 >=dev-texlive/texlive-basic-2024 >=dev-texlive/texlive-bibtexextra-2024 >=dev-texlive/texlive-binextra-2024 >=dev-texlive/texlive-context-2024 >=dev-texlive/texlive-fontsextra-2024 >=dev-texlive/texlive-fontsrecommended-2024 >=dev-texlive/texlive-fontutils-2024 >=dev-texlive/texlive-formatsextra-2024 >=dev-texlive/texlive-games-2024 >=dev-texlive/texlive-humanities-2024 >=dev-texlive/texlive-langarabic-2024 >=dev-texlive/texlive-langchinese-2024 >=dev-texlive/texlive-langcjk-2024 >=dev-texlive/texlive-langcyrillic-2024 >=dev-texlive/texlive-langczechslovak-2024 >=dev-texlive/texlive-langenglish-2024 >=dev-texlive/texlive-langeuropean-2024 >=dev-texlive/texlive-langfrench-2024 >=dev-texlive/texlive-langgerman-2024 >=dev-texlive/texlive-langgreek-2024 >=dev-texlive/texlive-langitalian-2024 >=dev-texlive/texlive-langjapanese-2024 >=dev-texlive/texlive-langkorean-2024 >=dev-texlive/texlive-langother-2024 >=dev-texlive/texlive-langpolish-2024 >=dev-texlive/texlive-langportuguese-2024 >=dev-texlive/texlive-langspanish-2024 >=dev-texlive/texlive-latex-2024 >=dev-texlive/texlive-latexextra-2024 >=dev-texlive/texlive-latexrecommended-2024 >=dev-texlive/texlive-luatex-2024 >=dev-texlive/texlive-mathscience-2024 >=dev-texlive/texlive-metapost-2024 >=dev-texlive/texlive-music-2024 >=dev-texlive/texlive-pictures-2024 >=dev-texlive/texlive-plaingeneric-2024 >=dev-texlive/texlive-pstricks-2024 >=dev-texlive/texlive-publishers-2024 >=dev-texlive/texlive-xetex-2024 The attached etc.portage.tar.xz has all details. ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10 [2] x86_64-pc-linux-gnu-14 * clang version 19.1.7 llvm-config: 19.1.7 Python 3.12.8 go version go1.23.5 linux/amd64 Available Ruby profiles: [1] ruby32 (with Rubygems) * Available Rust versions: [1] rust-bin-1.77.1 [2] rust-bin-1.81.0 [3] rust-bin-1.84.0 [4] rust-1.84.0 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 17.0.13_p11 [openjdk-bin-17] *) Eclipse Temurin JDK 21.0.5_p11 [openjdk-bin-21] 3) Eclipse Temurin JDK 8.432_p06 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-17 [3] openjdk-bin-21 system-vm HEAD of ::gentoo commit bd924ef2b951af8cab9549b226f777013b048137 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Tue Jan 21 15:48:31 2025 +0000 2025-01-21 15:48:30 UTC emerge -qpvO =net-libs/pjproject-2.15.1 [ebuild U ] net-libs/pjproject-2.15.1 [2.13.1-r1] USE="alsa epoll ffmpeg ilbc l16 libyuv opus portaudio sdl silk speex srtp ssl v4l2 -amr -debug -examples -g711 -g722 -g729 -g7221 -gsm -openh264 -resample -static-libs -vpx -webrtc"
Created attachment 917273 [details] emerge-info.txt
Created attachment 917274 [details] emerge-history.txt.xz
Created attachment 917275 [details] environment
Created attachment 917276 [details] etc.clang.tar.xz
Created attachment 917277 [details] etc.portage.tar.xz
Created attachment 917278 [details] logs.tar.xz
Created attachment 917279 [details] net-libs:pjproject-2.15.1:20250121-164252.log
Created attachment 917280 [details] qlist-info.txt.xz
Created attachment 917281 [details] temp.tar.xz
I'm also seeing this, are there any known workarounds anyone?
Not yet. Mind letting me know which compiler you're using? And USE flags?
Sure, I'm on sys-devel/gcc-14.2.1_p20241221 and CFLAGS="-O2 -pipe -march=znver4 -ggdb", USE="alsa amr ffmpeg g711 g722 g729 g7221 l16 openh264 opus portaudio resample sdl silk ssl vpx webrtc -debug -epoll -examples -gsm -ilbc -libyuv -speex -srtp -static-libs -v4l2"
With things like this I sometimes have to remove (emerge -C) the package and then it will compile fine. This has happened with me for this package, it was complaining when linking, but after removing it it merged clean.
(In reply to Jeremy Stent from comment #13) > With things like this I sometimes have to remove (emerge -C) the package and > then it will compile fine. This has happened with me for this package, it > was complaining when linking, but after removing it it merged clean. Ok, so this gives us a workaround, but not a fix. Suggestions/ideas?
(In reply to Jaco Kroon from comment #14) > (In reply to Jeremy Stent from comment #13) > > With things like this I sometimes have to remove (emerge -C) the package and > > then it will compile fine. This has happened with me for this package, it > > was complaining when linking, but after removing it it merged clean. > > Ok, so this gives us a workaround, but not a fix. Suggestions/ideas? I have not studied this, but I think it is when the link list gets scrambled so it finds the currently installed copies before it finds the ones just compiled. I think the build needs modified to adjust the link search order.
I can confirm that doing an emerge -C followed by emerge -1 produced no errors and the package was properly installed.
Thank you @ Jeremy Stent & @ George Diamantopoulos, emerge -C then emerge -1 did it for me also.
