On 2016-02-07, at 11:09 AM, Helge Deller wrote: >>> It would be great if someone with the necessary hardware could investigate >>> what causes this problem. >> >> For now I've installed the latest gcc version on the buildds and >> did a give-back on ffmpeg. If it fails again, I'll take a closer look. > > Yes, there seems to be a gcc bug/problem. > I've manually rebuilt ffmpeg-2.8.5-1 with gcc-5_5.3.1-8 and it fails the same > way (but it built earlier with gcc-5_5.3.1-6). > So, gcc-5_5.3.1-7 (and higher) currently have the problem.
There were no changes to the PA backend during this period but many changes to the core gcc code. In fact, the number of changes is somewhat surprising. > > Problem is (like you said) somewhere in the md5/crc code: > > TEST api-flac > /<<PKGBUILDDIR>>/tests/fate-run.sh fate-api-flac "" "" > "/<<PKGBUILDDIR>>/debian/standard" 'run tests/api/api-flac-test' 'null' > '/dev/null' '' '1' '' '' '' '' '' '' '' '' > /<<PKGBUILDDIR>>/debian/standard/tests/api/api-flac-test > Test api-flac failed. Look at tests/data/fate/api-flac.err for details. > channel layout: stereo, sample rate: 8000 > OK > channel layout: stereo, sample rate: 44100 > OK > channel layout: stereo, sample rate: 48000 > OK > channel layout: stereo, sample rate: 192000 > [flac @ 0x383b0] header crc mismatch > [flac @ 0x383b0] invalid frame header > [flac @ 0x383b0] decode_frame() failed > Error decoding audio packet > /<<PKGBUILDDIR>>/tests/Makefile:203: recipe for target 'fate-api-flac' failed We really need a testcase to isolate the problematic gcc change. Dave -- John David Anglin dave.ang...@bell.net
