Summary: | media-video/ffmpeg-0.6_p25423 fails src_test "Some tests in codectest failed" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kent Fredric (IRC: kent\n) (RETIRED) <kentnl> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Media-video project <media-video> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | Reimar.Doeffinger |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kent Fredric (IRC: kent\n) (RETIRED)
2010-10-20 04:44:44 UTC
What the...? Is the ebuild running the tests in a way that the newly compiled ffmpeg binary will use the installed libraries? Note that either you have to support tests only for statically linked versions or you will have to do whatever is necessary to make the OS select the newly compiled .so to run the FFmpeg binary. The build system doesn't take care of the latter since there is no way to do so in a portable way. (In reply to comment #1) > What the...? Is the ebuild running the tests in a way that the newly compiled > ffmpeg binary will use the installed libraries? Not sure. > Note that either you have to support tests only for statically linked versions > or you will have to do whatever is necessary to make the OS select the newly > compiled .so to run the FFmpeg binary. > The build system doesn't take care of the latter since there is no way to do so > in a portable way. > I tried with and without "static-libs" use flag, and it appeared to have no impact. I think I'll try a testless install of it and see what occurs. But my gut/instinct seems to think I'll get either a broken ffmpeg install, or that the ffmpeg build being used to run the tests differs from the one installed. > I tried with and without "static-libs" use flag
I don't think that will link the FFmpeg binary statically.
To test if this is the issue you'd have to set LD_LIBRARY_PATH to the directories where portage builds the libav*.so libraries (or disable compilation of the *.so completely, but I don't think the ebuild supports that).
(In reply to comment #1) > What the...? Is the ebuild running the tests in a way that the newly compiled > ffmpeg binary will use the installed libraries? yes; I updated LD_LIBRARY_PATH to know about libavcore when running the tests too so that this wont happen anymore Doesn't emerge run "make install" at some point? Wouldn't it then be simpler and safer to run the tests after that, since all libraries are then in the same path? Of course I don't expect FFmpeg to add libraries particularly often so it's a minor thing, but it seems nicer though. it would be simpler yes, but tests are ran before make install: http://devmanual.gentoo.org/ebuild-writing/functions/index.html so we do not really have a choice... It would not be impossible to have a pre-install and post-install test :-). Not claiming that this will actually make sense, just something worth considering if someone has the time and inclination... (In reply to comment #7) > It would not be impossible to have a pre-install and post-install test :-). > Not claiming that this will actually make sense, just something worth > considering if someone has the time and inclination... > It would be reasonably nasty, and I for one don't wish to see that happen. Running tests outside src_test(){ } sounds like fail to me. Getting it to work right with FEATURES="test" and FEATURES="-test", yuck. |