> From: Dale rdalek1967@gmail.com > Sent: Monday, October 23, 2023 12:47 PM > To: gentoo-user@lists.gentoo.org > Subject: Re: [gentoo-user] RE: libva-glx.so.2 > > Laurence Perkins wrote: > > From: Laurence Perkins lperkins@openeye.net > > Sent: Monday, October 23, 2023 11:05 AM > > To: gentoo-user@lists.gentoo.org > > Subject: [gentoo-user] libva-glx.so.2 > > > > I have a program with an embedded copy of ffmpeg that is choking on a lack of libva-glx.so.2. > > > > Debian has it in a libva-glx package. > > Manjaro has it in their general libva package. > > > > On Gentoo there is no trace of it... At least not until I use the 'ebuild' tool to build the libva package manually and sic 'find' on the compilation results. > > > > Then I find /var/tmp/portage/media-libs/libva-2.19.0/work/libva-2.19.0/va/.libs/libva-glx.so.2 > > > > So... apparently it builds the glx support libraries in a *hidden* folder? And I'm guessing then the ebuild's install phase fails to spot it? > > > > I'm thinking this is probably worthy of a bug report, but I want to make sure there's not some reason why these libraries are being left out on purpose first. Other distros have them, and I see at least one bug report about Steam now requiring it, so it probably needs sorting out somehow... > > > > > > LMP > > Bit of a followup. Poking around a bit more I find "-Dwith_glx=no" embedded in the ebuild. So apparently somebody back in the day decided it wasn't even worthy of a USE flag. I can tweak my own locally for now and will put a request for it on the bug tracker. > > LMP > > > If you not familiar with this site, you may want to check it out. It comes in handy when trying to find what file belongs to what package when you don't have it yet. > > https://www.portagefilelist.de/index.php > > I found this: > > https://www.portagefilelist.de/index.php?fs=*libva*glx*#panchor > > In case that link doesn't work, I searched for this. *libva*glx* It shows the following, for others who don't want to search. > > > Filename Filepath Category Package Version Arch > libva-glx.so.1.4000.0 /usr/lib64/libva-glx.so.1.4000.0 media-libs media-libs/libva-compat 1.8.3-r2 amd64 > libva-glx.so.1 /usr/lib64/libva-glx.so.1 media-libs media-libs/libva-compat 1.8.3-r2 amd64 > libva-glx.so.1.4000.0.debug /usr/lib/debug/usr/lib64/libva-glx.so.1.4000.0.debug media-libs media-libs/libva-compat 1.8.3-r2 amd64 > > > If that is the exact ones you are looking for, that's where they come from. > > Hope that helps. > > Dale > > :-) :-) > Well that's interesting... I have PFL installed on my systems so I can use the "e-file" command to search that database, but I was searching specifically for the libva-2.x version of it and so found nothing. Meanwhile, further digging has found https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e9eaf08653a2ada19b94c9807a6b85008a125b3c So apparently they turned it off back in April, but left it on in the libva-compat package since that doesn't cause circular dependency issues. Problem is that everyone else still uses it, so if you're running stuff that wasn't compiled on Gentoo it might not work as well as you might like. I'm going to ask nicely and see if we can have a USE flag for it. I'd really rather not maintain a fork of the ebuild for something so trivial. LMP