[FFmpeg-trac] #3133(undetermined:new): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC

[FFmpeg]

#3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC
-------------------------------------+-------------------------------------
             Reporter:  EricV        |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  important    |                Component:
              Version:  git-master   |  undetermined
             Keywords:  vdpau        |               Resolution:
  regression                         |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by ordroid):

 Replying to [comment:35 cehoyos]:
 > Replying to [comment:34 ordroid]:
 > > But for simplicitys sake I'll do --enable-shared :)
 >
 > Careful, because this may break other applications which expect
 libavcodec to be linked against certain libraries.
 > I am primarily (always) surprised about the --extra-cflags: I suspect
 they hurt performance, if they don't hurt performance, our configure
 script should be improved. Additionally, many options are the default
 (--enable-iconv) or make no sense on your architecture (--disable-altivec)
 or look contradictory to me (--disable-stripping --disable-debug). But as
 said all this is unrelated and it is much more failsafe if you continue
 using ebuild.
 Noted. On a further unrelated note, I've noticed that ffmpeg disables SSE
 and SSSE3 (from configure output) even though the CPU is capable of it
 (altivec and sse are USE flags and --disabled unless activated globally).
 Apparently it's slow on Atom - so not sure of the impact of those --extra
 compiler flags. I'll try removing them.

 But this is certainly unrelated, and I'm not sure how to progress. If you
 don't have any specific code points, I can start a binary search between
 bf36dc50 and a0c6c8e5 and try to nail down the commit that introduced it.
 Might take a while though :)

--
Ticket URL: <https://trac.ffmpeg.org/ticket/3133#comment:36>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker