too long lines were shrinked: >>> Source prepared. >>> Configuring source in /var/tmp/portage/media-video/ffmpeg-4.4.2/work/ffmpeg-4.4.2 ... * abi_x86_64.amd64: running multilib-minimal_abi_src_configure /var/tmp/portage/media-video/ffmpeg-4.4.2/work/ffmpeg-4.4.2/configure --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --docdir=/usr/share/doc/ffmpeg-4.4.2/html --mandir=/usr/share/man --enable-shared --cc=clang --cxx=clang++ --ar=x86_64-pc-linux-gnu-ar --nm=x86_64-pc-linux-gnu-nm --strip=x86 ERROR: vidstab >= 0.98 not found using pkg-config If you think configure made a mistake, make sure you are using the latest ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma_systemd-j4-20221004-150005 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-12.2.0 * clang/llvm (if any): clang version 15.0.2 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/15/bin Configuration file: /etc/clang/clang.cfg /usr/lib/llvm/15 15.0.2 Python 3.10.7 Available Ruby profiles: [1] ruby30 * Available Rust versions: [1] rust-bin-1.64.0 * The Glorious Glasgow Haskell Compilation System, version 9.0.2 php cli (if any): GNU Make 4.3 HEAD of ::gentoo commit 0fca2005b384a7ffe5b2bd00b7e1ccf801ece571 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Wed Oct 5 07:33:57 2022 +0000 2022-10-05 07:33:56 UTC emerge -qpvO media-video/ffmpeg [ebuild N ] media-video/ffmpeg-4.4.2 USE="X alsa bzip2 chromaprint dav1d encode flite gnutls gpl iconv lv2 mp3 network opencl opengl openh264 postproc sdl svg theora threads truetype vidstab vmaf vorbis x264 xvid zlib -amf -amr -amrenc (-appkit) -bluray -bs2b -cdio -chromium -codec2 -cpudetection (-cuda) -debug -doc -fdk -fontconfig -frei0r -fribidi -gcrypt -gme -gmp -gsm -hardcoded-tables -iec61883 -ieee1394 -jack -jpeg2k -kvazaar -ladspa -libaom -libaribb24 -libass -libcaca -libdrm -libilbc -librtmp -libsoxr -libtesseract -libv4l -libxml2 -lzma (-mipsdspr1) (-mipsdspr2) (-mipsfpu) (-mmal) -modplug -nvenc -openal -openssl -opus -oss -pic -pulseaudio -rav1e -rubberband -samba -snappy -sndio -speex -srt -ssh -static-libs -svt-av1 -test -twolame -v4l -vaapi -vdpau -verify-sig -vpx -vulkan -webp -x265 -zeromq -zimg -zvbi" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="aes avx avx2 fma3 mmx mmxext sse sse2 sse3 sse4_1 sse4_2 ssse3 -3dnow -3dnowext -fma4 -xop" FFTOOLS="aviocat cws2fws ffescape ffeval ffhash fourcc2pixfmt graph2dot ismindex pktdumper qt-faststart sidxindex trasher"
Created attachment 820873 [details] emerge-info.txt
Created attachment 820876 [details] emerge-history.txt
Created attachment 820879 [details] environment
Created attachment 820882 [details] etc.portage.tar.bz2
Created attachment 820885 [details] logs.tar.bz2
Created attachment 820888 [details] media-video:ffmpeg-4.4.2:20221005-082932.log
Created attachment 820891 [details] temp.tar.bz2
Just an 'FYI' comment. I ran into a similar issue with ffmpeg-6.x after I tried to build it with "...-vaapi..." In fact, I built mesa without "vaapi". I believe mesa provides many of the pkgconfig dependencies needed by ffmpeg, so although I was building ffmpeg[-vaapi] on top of mesa[-vaapi], ffmpeg still needed pkgconfig/packages that would have been provided by mesa had I built mesa with "vaapi". I tested this theory by rebuilding mesa with vaapi, which then installed more packages, and solved my ffmpeg[-vaapi] issue. To be fair, I never would have disabled vaapi anywhere except that vlc is still stuck on an ancient version of ffmpeg when vlc[vaapi] is built and causes a dependency conflict for ffmpeg. So now I'm just disabling vaapi for vlc only. I notice a lot of disabled USE flags for ffmpeg in this bug report...perhaps a w/a is to enable some of them for mesa and then try ffmpeg again. The dependency chain from ffmpeg -> mesa -> other-needed-packages is long and complex and may not even be solvable depending on how independent some of these features are. Good luck to whoever wants to tackle that...
Can't reproduce this, might either have been related to an older vidstab version (1.1.0-r1 is gone) or fixed in newer ffmpeg. Tentatively assuming this is obsolete, feel free to open a new one if it happens again and will check further then.
