| Summary: | media-libs/xine-lib-1.2.3: error: implicit declaration of function ‘av_free’ (w/ libav) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
| Component: | Current packages | Assignee: | Gentoo Media-video project <media-video> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | alan.mckinnon, atoth, patrizio.bassi, yamadharma |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | The build log | ||
|
Description
Michał Górny
2013-06-24 05:40:11 UTC
If I set USE="-vaapi" xine-lib compiles fine. exactly same issue here How is xine-lib-1.2.4? The same. Plus you should really kill this -Werror, you know. Well, it's -Werror-implicit-function-declaration not -Werror and I don't see any undefined reference w/ media-video/ffmpeg so this bug should really be fixed properly instead of ignoring it by removing -Werror-implicit-function-declaration Then fix it properly, or remove libav from the deps since it obviously does not work. (In reply to Michał Górny from comment #6) > Then fix it properly, or remove libav from the deps since it obviously does > not work. But it compiles fine with USE -vaapi even with libav. A sidenote on behalf of those users - including me - on libav. trying to understand the actual bug: av_free() is coming from libavutil/mem.h and the src/video_out/video_out_vaapi.c has: #ifdef HAVE_FFMPEG_AVUTIL_H # include <mem.h> #else # include <libavutil/mem.h> #endif and the mem.h looks okay in libav-9.9 sourcetree I just extracted :/ (In reply to Samuli Suominen from comment #8) > trying to understand the actual bug: > > av_free() is coming from libavutil/mem.h and the > src/video_out/video_out_vaapi.c has: > > #ifdef HAVE_FFMPEG_AVUTIL_H > # include <mem.h> > #else > # include <libavutil/mem.h> > #endif > > and the mem.h looks okay in libav-9.9 sourcetree I just extracted :/ It still fails to compile against libav-9.9. Removing vaapi USE flag is a possible workaround until this gets fixed. Any ideas to test? (In reply to Samuli Suominen from comment #8) > trying to understand the actual bug: > > av_free() is coming from libavutil/mem.h and the > src/video_out/video_out_vaapi.c has: > > #ifdef HAVE_FFMPEG_AVUTIL_H > # include <mem.h> > #else > # include <libavutil/mem.h> > #endif > > and the mem.h looks okay in libav-9.9 sourcetree I just extracted :/ xine-lib-1.2.4 now compiles fine against libav-9.9 with USE vaapi enabled. This new version will solve this issue. (In reply to Attila Tóth from comment #10) > (In reply to Samuli Suominen from comment #8) > > trying to understand the actual bug: > > > > av_free() is coming from libavutil/mem.h and the > > src/video_out/video_out_vaapi.c has: > > > > #ifdef HAVE_FFMPEG_AVUTIL_H > > # include <mem.h> > > #else > > # include <libavutil/mem.h> > > #endif > > > > and the mem.h looks okay in libav-9.9 sourcetree I just extracted :/ > > xine-lib-1.2.4 now compiles fine against libav-9.9 with USE vaapi enabled. > This new version will solve this issue. Yet in Comment #4 I'm hearing exactly different: https://bugs.gentoo.org/show_bug.cgi?id=474564#c4 (In reply to Samuli Suominen from comment #11) > (In reply to Attila Tóth from comment #10) > > xine-lib-1.2.4 now compiles fine against libav-9.9 with USE vaapi enabled. > > This new version will solve this issue. > > Yet in Comment #4 I'm hearing exactly different: > https://bugs.gentoo.org/show_bug.cgi?id=474564#c4 It fails for me (In reply to Samuli Suominen from comment #11) > (In reply to Attila Tóth from comment #10) > > (In reply to Samuli Suominen from comment #8) > > > trying to understand the actual bug: > > > > > > av_free() is coming from libavutil/mem.h and the > > > src/video_out/video_out_vaapi.c has: > > > > > > #ifdef HAVE_FFMPEG_AVUTIL_H > > > # include <mem.h> > > > #else > > > # include <libavutil/mem.h> > > > #endif > > > > > > and the mem.h looks okay in libav-9.9 sourcetree I just extracted :/ > > > > xine-lib-1.2.4 now compiles fine against libav-9.9 with USE vaapi enabled. > > This new version will solve this issue. > > Yet in Comment #4 I'm hearing exactly different: > https://bugs.gentoo.org/show_bug.cgi?id=474564#c4 Don't ask me. This was before libav-9.9, I guess. Now it seems to build. Attila may have something to say, though. (In reply to Michał Górny from comment #12) > Don't ask me. This was before libav-9.9, I guess. Now it seems to build. (In reply to Attila Tóth from comment #10) > xine-lib-1.2.4 now compiles fine against libav-9.9 with USE vaapi enabled. closing then as 'fixed by xine-lib-1.2.4 or libav-9.9, don't care which' |