Summary: | media-video/ffmpeg-6.1.1-r5 won't compile against x11-drivers/nvidia-drivers-550.78 after kernel update because of missing media-libs/nv-codec-headers files | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Valentin Saussois <valentin.saussois> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED NEEDINFO | ||
Severity: | minor | CC: | ionen, jstein, valentin.saussois |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Valentin Saussois
2024-05-30 17:01:20 UTC
That doesn't really make sense, nv-codec-headers is just headers that do not change (re-emerging just gets you the same thing). and nvidia-drivers is not needed to compile ffmpeg at all, it should not be impacting anything. What version of nv-codec-headers are you using, is it being pulled from an overlay or something? ::stefantalpalaru that you have in your list notably has it and may be the cause of your problems. (In reply to Ionen Wolkens from comment #1) > That doesn't really make sense, nv-codec-headers is just headers that do not > change (re-emerging just gets you the same thing). > > and nvidia-drivers is not needed to compile ffmpeg at all, it should not be > impacting anything. > > What version of nv-codec-headers are you using, is it being pulled from an > overlay or something? ::stefantalpalaru that you have in your list notably > has it and may be the cause of your problems. > That doesn't really make sense, nv-codec-headers is just headers that do not > change (re-emerging just gets you the same thing). > > and nvidia-drivers is not needed to compile ffmpeg at all, it should not be > impacting anything. > > What version of nv-codec-headers are you using, is it being pulled from an > overlay or something? ::stefantalpalaru that you have in your list notably > has it and may be the cause of your problems. (In reply to Ionen Wolkens from comment #1) You are right, when it happened I tried to emerge the previous versions available in my local tree and effectively the previous version was from "stefantalpalaru" overlay, and that's when the media-libs/nv-codec-headers have been dragged in my system. Then the ffmpeg-6.1.1-r5 successfully compile after... but maybe it's not what provided the necessary changes for the emerge to be successful. Sorry I've been too careless and hasty in my deductions. I encountered the problem just after I've updated my kernel before to get my system up to date before profile switching (17.1 -> 23.0) and at this moment ffmpeg failed to compile then after trying other version (and maybe compiling and rebooting to new kernel ?) succeeded. Now I'm at the end of emerge --emptytree -uDNav @world (and gentoo-soruces have been re emerged, I could have excluded it...) and ffmpeg-6.1.1-r5 compilation is acting-up again with the same error. I'm getting back to this bug report when I'll really get to the bottom of this. Sorry for the noise. Thank you. I suggest, you open a new ticket then with all information at hand. I will close this one here so you have a clean new ticket then. If you want, we can help you to locate the problem in our support channels https://www.gentoo.org/support/ |