[FFmpeg-devel] qt-faststart bug near 4GB

[Eran Kornblau]

> 
> -----Original Message-----
> From: ffmpeg-devel [mailto:ffmpeg-devel-bounces at ffmpeg.org] On Behalf Of Michael Niedermayer
> Sent: Wednesday, June 13, 2018 12:26 AM
> To: FFmpeg development discussions and patches <ffmpeg-devel at ffmpeg.org>
> Subject: Re: [FFmpeg-devel] qt-faststart bug near 4GB
> 
> fails on mingw64 + wine
> 
> make fate-mov-faststart-4gb-overflow V=2
> --- -	2018-06-12 23:23:10.487549933 +0200
> +++ tests/data/fate/mov-faststart-4gb-overflow	2018-06-12 23:23:10.479161196 +0200
> @@ -1 +0,0 @@
> -bc875921f151871e787c4b4023269b29
> Test mov-faststart-4gb-overflow failed. Look at tests/data/fate/mov-faststart-4gb-overflow.err for details.
> run-detectors: unable to find an interpreter for tools/qt-faststart.exe
> md5sum: faststart-4gb-overflow-output.mov: No such file or directory
> rm: cannot remove 'faststart-4gb-overflow-output.mov': No such file or directory
> make: *** [fate-mov-faststart-4gb-overflow] Error 1
> 
I fought for some time today trying to get this env set up, and lost... :(

But I now noticed that when I wrote this test, at some point I dropped the 
'run' from CMD. On my env, it works both with 'run' and without it, 
maybe on mingw64 it's required (sorry, not familiar with the test framework)

The attached patch is the identical to the previous, except for the addition
of 'run'. 
Can you try it?

Thanks

Eran

> 
> [...]
> 
> -- 
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
> 
> It is dangerous to be right in matters on which the established authorities are wrong. -- Voltaire
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-qt-faststart-add-fate-test-for-stco-overflow.patch
Type: application/octet-stream
Size: 3151 bytes
Desc: 0001-qt-faststart-add-fate-test-for-stco-overflow.patch
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20180613/cf1eddea/attachment.obj>