The transcode build assumes the ffmpeg headers are in ffmpeg/, but they are in libavcodec/ instead, so configure whines about them being missing. I attach a stupid, ugly and brute-force patch to the ebuild that works nicely over here. This could also be an issue of other versions of transcode (haven't tried though). I have no idea if this is a upstream transcode or ffmpeg issue. Cheers, Benjamin
Created attachment 157969 [details, diff] sed for correct include paths
Sorry, one important piece of information I forget: ffmpeg is at media-video/ffmpeg-0.4.9_p20080326 here.
It is because you are mixing branches: stable transcode with testing (~arch) ffmpeg version. ~transcode-1.0.4 works with ~ffmpeg-0.4.9_p20070616, if you use ffmpeg-0.4.9_p20080326 you should use transcode-1.0.6_rc2-r1 with that. See bug 214740. The ffmpeg dependency for <=transcode-1.0.5-r2 needs an update to prevent this mixing.
+ 29 Jun 2008; Peter Alfredsen <loki_val@gentoo.org> transcode-1.0.4.ebuild, + transcode-1.0.4-r2.ebuild, -transcode-1.0.5-r2.ebuild: + Fix deps for ffmpeg wrt bug #228833. +