Bug 329655 – www-client/chromium-9999 build failure - 'struct AVFrame' has no member 'owner'

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Mike Gilbert 2010-07-23 23:21:59 UTC]

Chromium build fails with following message:

media/filters/ffmpeg_video_allocator.cc: In member function ‘void media::FFmpegVideoAllocator::Stop(AVCodecContext*)’:
media/filters/ffmpeg_video_allocator.cc:40: error: ‘struct AVFrame’ has no member named ‘owner’
media/filters/ffmpeg_video_allocator.cc:41: error: ‘struct AVFrame’ has no member named ‘owner’
media/filters/ffmpeg_video_allocator.cc: In member function ‘void media::FFmpegVideoAllocator::DisplayDone(AVCodecContext*, scoped_refptr<media::VideoFrame>)’:
media/filters/ffmpeg_video_allocator.cc:55: error: ‘struct AVFrame’ has no member named ‘owner’
make: *** [out/Release/obj.target/media/media/filters/ffmpeg_video_allocator.o] Error 1

The file ffmpeg_video_allocator.cc was added in changeset 53418:
http://src.chromium.org/viewvc/chrome?view=rev&revision=53418

The new code is referencing a struct member that only exists in Chromium's fork of ffmpeg (ffmpeg-mt). The relevant struct (AVFrame) is declared in libavcodec/avcodec.h.

I have tried building with both ffmpeg-0.6 and ffmpeg-9999 from portage; the error is the same.

[Comment 1 Paweł Hajdan, Jr. (RETIRED) 2010-07-24 17:58:53 UTC]

Thanks for the early warning. I think I'll handle this when the next dev channel build is released.

[Comment 2 Paweł Hajdan, Jr. (RETIRED) 2010-07-25 23:14:02 UTC]

*** Bug 329759 has been marked as a duplicate of this bug. ***

[Comment 3 Mike Gilbert 2010-07-26 05:14:54 UTC]

Created attachment 240179 [details, diff]
Disable system ffmpeg

In case anyone is looking for a quick fix in the mean time, this patch will disable system ffmpeg usage and install the bundled library instead.

[Comment 4 Paweł Hajdan, Jr. (RETIRED) 2010-07-28 03:52:20 UTC]

I think the upstream has fixed it. Can anyone confirm?

[Comment 5 Mike Gilbert 2010-07-28 05:33:13 UTC]

(In reply to comment #4)
> I think the upstream has fixed it. Can anyone confirm?
> 

I can confirm that this is working for me again.  It looks like they removed the new file from the build scripts:

http://codereview.chromium.org/2873068

[Comment 6 Paweł Hajdan, Jr. (RETIRED) 2010-07-28 14:56:30 UTC]

Thanks, closing.