SOCKSv5: fix inverted logic (fixes #10247)
mmdevice: cosmetic
Do not activate YUVA422P in FFmpeg until 51.74.100

From 51.49.100 to 51.74.100, it only defines PIX_FMT_YUVA422P and not
AV_PIX_FMT_YUVA422P. There are other ways to fix, but ugly. And people should
update their FFmpeg anyway :)
Fix FFv1 output with FFmpeg

Close #8691

Of course, because we _really_ need that many RGB formats...
avcodec: Always output frames

With the introduction of CODEC_FLAG_OUTPUT_CORRUPT incomplete frames
are silently dropped. Enable it to maintain the previous behaviour.

Close #10140

Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>
Contrib: use a simpler way to discriminate between libav and FFmpeg
Direct3D: less verbose output
posix: simplify thread error handler
vlc_strerror() and vlc_strerror_c() convenience wrappers

Those are more flexible than the GNU-specific %m format specifier to
print standard error messages. They are also less likely to format a
clobbered error number.
win32: implement vlc_strerror and vlc_strerror_c
src: use vlc_strerror_c() for log messages
file: use vlc_strerror()

This fixes "%m" in error dialogs on non-GNU platforms.
libav: use vlc_strerror_c()
DTV: use vlc_strerror_c()
DV: use vlc_strerror_c()
DVB (old): use vlc_strerror_c()
MMS: use vlc_strerror_c()
MTP: use vlc_strerror() & vlc_strerror_c()
linsys: use vlc_strerror_c()
OSS: use vlc_strerror_c()