Re: Bug#638250: Bug#639948: Bug#638250: Needs to be adapted for libav/0.7
* Reinhard Tartler [110904 12:07 +0200]:
> On Sun, Sep 04, 2011 at 11:23:34 (CEST), Elimar Riesebieter wrote:
> > * Reinhard Tartler [110904 08:47 +0200]:
> >> tags 638250 help
> >> stop
> >> On Sun, Sep 04, 2011 at 06:45:36 (CEST), Elimar Riesebieter wrote:
> >> > block 638250 by 639948
> >> > thanks
> >> I strongly disagree that this arch specific defect on ppc is in any way
> >> a blocking bug for recompiling moc-ffmpeg-plugin against the new libav
> >> libraries.
> > moc-ffmpeg-plugin on ppc compiles well against libav 0.7.1 libraries
> > but produces exactly the same backtraces as ffplay 0.7.1 on ppc. So
> > this is surely a libav bug.
> Nobody doubts that. My objection in that the 'block' relationship is
> wrong. As soon as a change for the altivec assembler code is found,
> surely moc-ffmpeg-plugin will work again.
> >> It only affects (some?) altivec enabled machines and can be
> >> easily avoided by disabling the altivec variant.
> > What do you mean with only? PPC is an officialy supported
> > architecture in Debian!
> I mean that we know that the bug appears on your particular machine. I
> question that it might not be broken on *every* altivec machine
> available. The code in question has passed an intensive regression
> suite, which includes testing on altivec machines. I'm curious how this
> could slip through:
These builds were done with "--enable-gpl --cpu=g4 --cc=gcc-4.6.1"
only, which are totaly different from Debians build so are not
The Debian package 0.7.1-4 builds well on my "particular machine"
but coredumps with ffplay...
The path to source is always uphill!