Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 218088 - Prepare media-plugins/alsa-plugins apps to use newer ffmpeg
Summary: Prepare media-plugins/alsa-plugins apps to use newer ffmpeg
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo ALSA team
URL:
Whiteboard:
Keywords:
: 233975 (view as bug list)
Depends on:
Blocks: 214740
  Show dependency tree
 
Reported: 2008-04-17 12:57 UTC by Ben de Groot (RETIRED)
Modified: 2008-08-07 01:35 UTC (History)
7 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
patch to accept new ffmpeg layout (new-ffmpeg.patch,1.00 KB, patch)
2008-08-05 22:13 UTC, Rafał Mużyło
Details | Diff
corrected patch (new-ffmpeg.patch,1.58 KB, patch)
2008-08-05 22:20 UTC, Rafał Mużyło
Details | Diff
Patch after 1.0.17-automagic (bug218088b.patch,1.97 KB, patch)
2008-08-06 17:38 UTC, Martin von Gagern
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Ben de Groot (RETIRED) gentoo-dev 2008-04-17 12:57:01 UTC
FFmpeg recently changed all the include paths. Every application using it
should update. Make sure the applications build against currently hardmasked media-video/ffmpeg-0.4.9_p20080326.

Alsa herd:
media-plugins/alsa-plugins
Comment 1 Ben de Groot (RETIRED) gentoo-dev 2008-06-13 11:51:44 UTC
works with 1.0.16 (latest stable)
Comment 2 Graham Murray 2008-08-03 17:32:00 UTC
(In reply to comment #1)
> works with 1.0.16 (latest stable)
> 
But broken again in 1.0.16 and new 1.0.17 by today's updates.
Comment 3 Ben de Groot (RETIRED) gentoo-dev 2008-08-05 13:32:11 UTC
I'm reopening this, as quite a few users run into this issue. Preferably at least the most recent ~arch version (1.0.17 at this point) should be patched to work with newer ffmpeg.
Comment 4 Ben de Groot (RETIRED) gentoo-dev 2008-08-05 13:35:18 UTC
*** Bug 233975 has been marked as a duplicate of this bug. ***
Comment 5 Dan Coats 2008-08-05 16:21:06 UTC
ffmpeg? ( <=media-video/ffmpeg-0.4.9_p20080326 )
works fine for me
Comment 6 Jeff Mitchell 2008-08-05 17:47:56 UTC
The problem I ran into was that the dependency seemed to have been changed in the stable non-arch 1.0.16 ebuild without bumping it to a -r version.  This caused emerge to fail, but an equery showed that I should have been fine, probably because it was using dependency info from the old cached 1.0.16 ebuild.

I'd like to recommend 1.0.16 stable be bumped to a -r version to keep anyone else from bumping into this.
Comment 7 Ben de Groot (RETIRED) gentoo-dev 2008-08-05 19:07:19 UTC
Petteri, the ChangeLog says you disabled newer ffmpeg for 1.0.16. I'm wondering in which way it does not work?
Comment 8 Petteri Räty (RETIRED) gentoo-dev 2008-08-05 20:20:46 UTC
(In reply to comment #7)
> Petteri, the ChangeLog says you disabled newer ffmpeg for 1.0.16. I'm wondering
> in which way it does not work?
> 

pena alsa-plugins # USE="ffmpeg" devebuild alsa-plugins-1.0.16.ebuild clean compile

checking for ffmpeg/avcodec.h... no

A52, lavc plugins:  no
Comment 9 Rafał Mużyło 2008-08-05 22:13:28 UTC
Created attachment 162314 [details, diff]
patch to accept new ffmpeg layout

Just to be annoying:
with this patch it seems to build just fine
with the new header layout.
No clue if it actually works,
but `ldd -r` doesn't complain,
so it should be OK.
Comment 10 Rafał Mużyło 2008-08-05 22:20:44 UTC
Created attachment 162318 [details, diff]
corrected patch

Sorry, missed a52 in the first one.
Comment 11 Martin von Gagern 2008-08-06 17:38:03 UTC
Created attachment 162377 [details, diff]
Patch after 1.0.17-automagic

(In reply to comment #10)
Your patch interferes with alsa-plugins-1.0.17-automagic.patch.
This one here takes care of that if applied after the automagic one.
Comment 12 Ben de Groot (RETIRED) gentoo-dev 2008-08-06 22:39:52 UTC
Thanks for your contributions. Patch is applied to 1.0.17-r1.
Comment 13 Jeff Mitchell 2008-08-07 01:35:14 UTC
This is not fixed.  You didn't address comment #6, which was reported in bug 233975 and (perhaps wrongly) marked as a duplicate of this one.