Summary: | net-libs/pjproject-2.15.1 - [texlive] [ffmpeg] fifobuf.c:(<snip>) undefined reference to pj_fifobuf_capacity | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Jaco Kroon <jaco> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | georgediam, jaco, stentj, yuyuyak |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
emerge-history.txt.xz environment etc.clang.tar.xz etc.portage.tar.xz logs.tar.xz net-libs:pjproject-2.15.1:20250121-164252.log qlist-info.txt.xz temp.tar.xz |
Description
Toralf Förster
![]() 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. |