[FFmpeg-devel] [PATCH] Remove printf format string errors in windows builds

Ronald S. Bultje rsbultje
Mon Jan 24 03:06:34 CET 2011


Hi,

On Sun, Jan 23, 2011 at 9:03 PM, JonY <jon_y at users.sourceforge.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 1/24/2011 09:55, Ronald S. Bultje wrote:
>> Hi,
>>
>> On Sun, Jan 23, 2011 at 8:21 PM, Larry Robinson <silver-dad at comcast.net> wrote:
>>> Jean-Baptiste Kempf for pointing this out), but this is not yet implemented
>>> for sscanf in Mingw-w64.
>>>
>>> What breaks is a number of error messages which will print incorrectly, but
>>> for a successful run these sections of code are not executed.
>>
>> bash-3.2$ grep -r sscanf .. 2>&1 | grep -v matches | grep %z
>> bash-3.2$ grep -r sscanf .. 2>&1 | grep -v matches | grep %t
>> bash-3.2$
>>
>> I don't see a problem.
>>
>
> Hi,
>
> So, ffmpeg doesn't use any scanf format that msvcrt doesn't understand?

I indeed think ffmpeg does not use such scanf formats. We only use
%z/%t/etc for printf(), av_log() etc.

Ronald



More information about the ffmpeg-devel mailing list