Re: [FFmpeg-devel] [PATCH v2 3/3] avformat/dashenc: configuring container format options

Pushed. On 5/7/18 3:28 PM, vdi...@akamai.com wrote: > From: Vishwanath Dixit > > --- > doc/muxers.texi | 4 > libavformat/dashenc.c | 7 +++ > 2 files changed, 11 insertions(+) > > diff --git a/doc/muxers.texi b/doc/muxers.texi > index db81901..e9082a4 100644 >

Re: [FFmpeg-devel] [PATCH 2/3] lavu/Makefile: Fix alignment and ordering

On 5/14/18, Mark Thompson wrote: > --- > libavutil/Makefile | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > ok ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

[FFmpeg-devel] [PATCH] [WIP] libopusdec: Enable FEC/PLC

Whenever we detect a discontinuity in the incoming stream, ask libopus to make up intermediate frames based on the first one we actually have after the discontinuity. If the stream contains FEC data (basically a low-quality side stream that is delayed by one packet), libopus will decode that. If

Re: [FFmpeg-devel] [PATCH v6 1/3] avcodec: add flags for packets with top/bottom field

On Mon, 14 May 2018 18:26:35 -0400 Patrick Keroulas wrote: > Signed-off-by: Patrick Keroulas > --- > doc/APIchanges | 3 +++ > libavcodec/avcodec.h | 8 > libavcodec/version.h | 4 ++-- > 3 files

[FFmpeg-devel] [PATCH 1/2] avformat/mov: Break out early if chunk_count is 0 in mov_build_index()

Without this some operations might overflow (undefined behavior) even though the index adding loop would never execute No testcase known Signed-off-by: Michael Niedermayer --- libavformat/mov.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/libavformat/mov.c

Re: [FFmpeg-devel] [PATCH 3/3] hwcontext: Add test for device creation and derivation

On Tue, May 15, 2018 at 11:31 AM, Mark Thompson wrote: > > I think that means there should be something gating this test (and any other > hardware tests) - how about a configure option --(en|dis)able-hw-tests, with > default value the same as autodetect? (I think that has the

Re: [FFmpeg-devel] [PATCH] avutil/hwcontext_cuda: fix YUV420P cuda_get_buffer

On Tue, 15 May 2018, Timo Rothenpieler wrote: On 14.05.2018 23:29, Marton Balint wrote: Regression since ece068a771ac3f725e854c681ecbef08e792addc. Signed-off-by: Marton Balint --- libavutil/hwcontext_cuda.c | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-)

Re: [FFmpeg-devel] [PATCH] avutil/hwcontext_cuda: fix YUV420P cuda_get_buffer

On 14.05.2018 23:29, Marton Balint wrote: > Regression since ece068a771ac3f725e854c681ecbef08e792addc. > > Signed-off-by: Marton Balint > --- > libavutil/hwcontext_cuda.c | 9 ++--- > 1 file changed, 6 insertions(+), 3 deletions(-) > > diff --git

[FFmpeg-devel] [PATCH 2/2] avformat/mov: Only fail for STCO/STSC contradictions if both exist

Fixes regression with playback of GF9720Repeal20the20Eighth20with20Helen20Linehan.m4a See: crbug 822666 Found-by: "Mattias Wadman Signed-off-by: Michael Niedermayer --- libavformat/mov.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

> I'm leaning toward 2, but there would need to be some other way to deal > with people not getting along. Maybe Mumble conferences where the > involved parties get to air their feelings on whatever is at issue? I > dunno I'm not weighing in on the CoC so much as offering my experience with other

Re: [FFmpeg-devel] avformat/mpegts: set AV_DISPOSITION_DESCRIPTIONS for OIPF cases

I have prepared a testcase. PMT data comes from org.hbbtv_HTML50420 - I have squashed them and there is one file attached now. Please review. Regards, *Łukasz Krzciuk* Developer Vewd ul. Grabarska 2, Pegaz 2A, 50-079 Wrocław, Polska On Mon, May 14, 2018 at 10:23 AM, Łukasz Krzciuk

Re: [FFmpeg-devel] [PATCH] avformat/mpegts: add merge_pmt_versions option

On Mon, May 14, 2018 at 03:54:01PM -0700, Aman Gupta wrote: > From: Aman Gupta > > This new optional flag makes it easier to deal with mpegts > samples where the PMT is updated and elementary streams move > to different PIDs in the middle of playback. > > Previously, new

Re: [FFmpeg-devel] [PATCH 3/3] hwcontext: Add test for device creation and derivation

On 15/05/18 03:16, Michael Niedermayer wrote: > On Mon, May 14, 2018 at 10:58:58PM +0100, Mark Thompson wrote: >> This uses any devices it can find on the host system - on a system with no >> hardware device support or in builds with no support included it will do >> nothing and pass. >> --- >>

Re: [FFmpeg-devel] [PATCH 3/3] hwcontext: Add test for device creation and derivation

On Tue, May 15, 2018 at 11:36:13AM +0200, Hendrik Leppkes wrote: > On Tue, May 15, 2018 at 11:31 AM, Mark Thompson wrote: > > > > I think that means there should be something gating this test (and any > > other hardware tests) - how about a configure option > >

Re: [FFmpeg-devel] [PATCH] avutil/hwcontext_cuda: fix YUV420P cuda_get_buffer

On 15.05.2018 13:37, Marton Balint wrote: >> Are you sure it isn't already that way? I tested specially YUV420P and >> could not make out any issues. > > For 4K content linesize[0] is 3840, but linesize[1] becomes 2048 instead > of 1920. That's odd, 2048 seems more correct since it's a multiple

Re: [FFmpeg-devel] [PATCH 3/3] hwcontext: Add test for device creation and derivation

On 15/05/18 03:16, Xiang, Haihao wrote: > On Mon, 2018-05-14 at 22:58 +0100, Mark Thompson wrote: >> This uses any devices it can find on the host system - on a system with no >> hardware device support or in builds with no support included it will do >> nothing and pass. >> --- >>

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

mån 2018-05-14 klockan 17:50 +0100 skrev Derek Buitenhuis: > Hello all. > > [...] > > So, I present to you two possible options: > > 1. Implement a formal CoC enforcement system. This has been mostly > copypasted >    from VideoLAN's, and is meant as more of a blueprint. This will no

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

tis 2018-05-15 klockan 09:10 -0400 skrev Devin Heitmueller: > > I'm leaning toward 2, but there would need to be some other way to deal > > with people not getting along. Maybe Mumble conferences where the > > involved parties get to air their feelings on whatever is at issue? I > > dunno > > I'm

Re: [FFmpeg-devel] [PATCH v6 1/3] avcodec: add flags for packets with top/bottom field

On 15 May 2018 at 15:55, wm4 wrote: > On Mon, 14 May 2018 18:26:35 -0400 > Patrick Keroulas wrote: > > > Signed-off-by: Patrick Keroulas > > --- > > doc/APIchanges | 3 +++ > >

Re: [FFmpeg-devel] [PATCH v6 1/3] avcodec: add flags for packets with top/bottom field

On Tue, 15 May 2018 17:15:05 +0100 Rostislav Pehlivanov wrote: > On 15 May 2018 at 15:55, wm4 wrote: > > > On Mon, 14 May 2018 18:26:35 -0400 > > Patrick Keroulas wrote: > > > > > Signed-off-by: Patrick

[FFmpeg-devel] [PATCH] avformat/mpegts: tag video streams with still images

From: Aman Gupta Parses the video_stream_descriptor (H.222 2.6.2) to look for the still_picture_flag. This is exposed to the user via a new AV_DISPOSITION_STILL_IMAGE. See for example https://tmm1.s3.amazonaws.com/music-choice.ts, whose video stream only updates every ~6 seconds.

[FFmpeg-devel] [PATCH v2] avformat/mpegts: add merge_pmt_versions option

From: Aman Gupta This new optional flag makes it easier to deal with mpegts samples where the PMT is updated and elementary streams move to different PIDs in the middle of playback. Previously, new AVStreams were created per PID, and it was up to the user to figure out which

Re: [FFmpeg-devel] [PATCH] mov: Make sure PTS are both monotonically increasing, and unique

tis 2018-05-15 klockan 20:44 +0100 skrev Derek Buitenhuis: > We already did this for audio, but it should be done for video too. > If we don't, seeking back to the start of the file, for example, can > become quite broken, since the first N packets will have repeating > and nonmonotonic PTS, yet

Re: [FFmpeg-devel] [PATCH] avformat/mpegts: add merge_pmt_versions option

On Tue, May 15, 2018 at 5:12 AM, Michael Niedermayer wrote: > On Mon, May 14, 2018 at 03:54:01PM -0700, Aman Gupta wrote: > > From: Aman Gupta > > > > This new optional flag makes it easier to deal with mpegts > > samples where the PMT is updated and

Re: [FFmpeg-devel] [PATCH 3/5] examples/filtering_video: add missing headers

On Mon, May 14, 2018 at 08:18:00PM +0800, Zhao Zhili wrote: > From: Zhao Zhili > > --- > doc/examples/filtering_video.c | 2 ++ > 1 file changed, 2 insertions(+) will apply thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Dictatorship

Re: [FFmpeg-devel] [PATCH 2/5] examples/filtering_video: drop an always true condition

On Mon, May 14, 2018 at 08:17:59PM +0800, Zhao Zhili wrote: > From: Zhao Zhili > > --- > doc/examples/filtering_video.c | 34 -- > 1 file changed, 16 insertions(+), 18 deletions(-) will apply thx [...] -- Michael GnuPG fingerprint:

Re: [FFmpeg-devel] [PATCH v6 1/3] avcodec: add flags for packets with top/bottom field

On Tue, May 15, 2018 at 05:15:05PM +0100, Rostislav Pehlivanov wrote: > On 15 May 2018 at 15:55, wm4 wrote: > > > On Mon, 14 May 2018 18:26:35 -0400 > > Patrick Keroulas wrote: > > > > > Signed-off-by: Patrick Keroulas

Re: [FFmpeg-devel] [PATCH v6 1/3] avcodec: add flags for packets with top/bottom field

On 15 May 2018 at 18:03, wm4 wrote: > On Tue, 15 May 2018 17:15:05 +0100 > Rostislav Pehlivanov wrote: > > > On 15 May 2018 at 15:55, wm4 wrote: > > > > > On Mon, 14 May 2018 18:26:35 -0400 > > > Patrick Keroulas

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

On Mon, May 14, 2018 at 7:50 PM, Derek Buitenhuis wrote: > > So, I present to you two possible options: > > 1. Implement a formal CoC enforcement system. This has been mostly > copypasted >from VideoLAN's, and is meant as more of a blueprint. This will no

Re: [FFmpeg-devel] [PATCH] avfilter: add aderivative and aintegral filter

On 5/14/18, Paul B Mahol wrote: > Signed-off-by: Paul B Mahol > --- > doc/filters.texi | 6 ++ > libavfilter/Makefile | 2 + > libavfilter/af_aderivative.c | 207 > +++ > libavfilter/allfilters.c

Re: [FFmpeg-devel] [PATCH v6 1/3] avcodec: add flags for packets with top/bottom field

On Mon, May 14, 2018 at 11:26 PM, Patrick Keroulas wrote: > Signed-off-by: Patrick Keroulas > --- > doc/APIchanges | 3 +++ > libavcodec/avcodec.h | 8 > libavcodec/version.h | 4 ++-- > 3 files

Re: [FFmpeg-devel] [PATCH 5/5] doc/examples: add missing ignore files

On Mon, May 14, 2018 at 08:18:02PM +0800, Zhao Zhili wrote: > From: Zhao Zhili > > --- > doc/examples/.gitignore | 2 ++ > 1 file changed, 2 insertions(+) will apply thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB While the State

Re: [FFmpeg-devel] [PATCH 4/5] examples/filtering_video: fix memory leak

On Mon, May 14, 2018 at 08:18:01PM +0800, Zhao Zhili wrote: > From: Zhao Zhili > > --- > doc/examples/filtering_video.c | 15 +-- > 1 file changed, 9 insertions(+), 6 deletions(-) will apply [...] -- Michael GnuPG fingerprint:

[FFmpeg-devel] [PATCH] mov: Make sure PTS are both monotonically increasing, and unique

We already did this for audio, but it should be done for video too. If we don't, seeking back to the start of the file, for example, can become quite broken, since the first N packets will have repeating and nonmonotonic PTS, yet they need to be decoded even if they are to be discarded.

Re: [FFmpeg-devel] [PATCH] mov: Make sure PTS are both monotonically increasing, and unique

On Tue, May 15, 2018 at 9:10 PM, Tomas Härdin wrote: > Why don't we do this for every format? In this case, it is specific to MOV and MP4, since it's caused by the way we apply edit lists at the packet level (reordering, marking them as discard, changing timestamps, etc.).

Re: [FFmpeg-devel] [PATCH] mov: Make sure PTS are both monotonically increasing, and unique

tis 2018-05-15 klockan 21:21 +0100 skrev Derek Buitenhuis: > On Tue, May 15, 2018 at 9:10 PM, Tomas Härdin > wrote: > > Why don't we do this for every format? > > In this case, it is specific to MOV and MP4, since it's caused by the > way we apply edit lists at the packet

Re: [FFmpeg-devel] [PATCH] avformat/mpegts: add merge_pmt_versions option

On Tue, May 15, 2018, 15:12 Michael Niedermayer wrote: > On Mon, May 14, 2018 at 03:54:01PM -0700, Aman Gupta wrote: > > From: Aman Gupta > > > > This new optional flag makes it easier to deal with mpegts > > samples where the PMT is updated and elementary

Re: [FFmpeg-devel] [PATCH 2/2] avformat/mov: Only fail for STCO/STSC contradictions if both exist

2018-05-15 17:07 GMT+02:00, Michael Niedermayer : > Fixes regression with playback of > GF9720Repeal20the20Eighth20with20Helen20Linehan.m4a > See: crbug 822666 Please mention ticket #7165 if related. Thank you, Carl Eugen ___

Re: [FFmpeg-devel] FIX: HLS Discontinuity / Non-Monotonous DTS

On Tue, Mar 20, 2018 at 7:46 AM, Joe Koberg wrote: > On Fri, Mar 16, 2018 at 11:14 AM, Carl Eugen Hoyos > wrote: > > 2018-03-16 16:07 GMT+01:00, Joe Koberg : > >> On Fri, Mar 16, 2018 at 10:48 AM, Carl Eugen Hoyos > >>

Re: [FFmpeg-devel] [PATCH v2 0/3] Enhancement NAL type debug

2018-05-14 17:45 GMT+08:00 Jun Zhao : > v2: - cover all h264/hevc NAL unit type > - use table replace switch when map NAL type to string/name > > Jun Zhao (3): > lavc/h2645_parse: log more HEVC NAL type. > lavc/h2645_parse: rename the nal_unit_name to

[FFmpeg-devel] [PATCH v2] hwcontext: Add test for device creation and derivation

This uses any devices it can find on the host system - on a system with no hardware device support or in builds with no support included it will do nothing and pass. --- It now comes under a new target "fate-hw", which is not run as part of "fate". I found the CMP option, so it no longer has a

[FFmpeg-devel] [PATCH] avformat/error_resilience: Allow file to be included in c++ programs

From: Peter Bennett The header stdatomic.h causes compile errors in a c++ compiler, even when extern "C" is used around it. The appropriate c++ include is . We cannot use #include inside error_resilience.h because that causes compile errors inside extern "C". With this

Re: [FFmpeg-devel] [PATCH] avformat/error_resilience: Allow file to be included in c++ programs

On 5/15/2018 9:25 PM, Peter Bennett wrote: > From: Peter Bennett > > The header stdatomic.h causes compile errors in a c++ compiler, even > when extern "C" is used around it. The appropriate c++ include is . > We cannot use #include inside error_resilience.h because that

Re: [FFmpeg-devel] [PATCH] avformat/error_resilience: Allow file to be included in c++ programs

2018-05-16 2:25 GMT+02:00, Peter Bennett : > From: Peter Bennett > > The header stdatomic.h causes compile errors in a c++ compiler, even > when extern "C" is used around it. The appropriate c++ include is . > We cannot use #include inside

Re: [FFmpeg-devel] [PATCH] avformat/error_resilience: Allow file to be included in c++ programs

On 05/15/2018 08:44 PM, James Almer wrote: On 5/15/2018 9:25 PM, Peter Bennett wrote: From: Peter Bennett The header stdatomic.h causes compile errors in a c++ compiler, even when extern "C" is used around it. The appropriate c++ include is . We cannot use #include

Re: [FFmpeg-devel] [PATCH] avformat/error_resilience: Allow file to be included in c++ programs

On 5/15/2018 9:49 PM, Peter Bennett wrote: > > > On 05/15/2018 08:44 PM, James Almer wrote: >> On 5/15/2018 9:25 PM, Peter Bennett wrote: >>> From: Peter Bennett >>> >>> The header stdatomic.h causes compile errors in a c++ compiler, even >>> when extern "C" is used around

Re: [FFmpeg-devel] [PATCH] [WIP] libopusdec: Enable FEC/PLC

On Tue, May 15, 2018 at 12:35:45AM +0200, Steinar H. Gunderson wrote: > Whenever we detect a discontinuity in the incoming stream, ask libopus > to make up intermediate frames based on the first one we actually have > after the discontinuity. If the stream contains FEC data (basically a >

[FFmpeg-devel] [PATCH] avformat: Fix errors in version script list

From: Peter Bennett libavformat.v has url_open, url_close and url_write. These should be ffurl_ in each case. --- libavformat/libavformat.v | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/libavformat/libavformat.v b/libavformat/libavformat.v index

Re: [FFmpeg-devel] [PATCH] avformat/error_resilience: Allow file to be included in c++ programs

On 05/15/2018 08:58 PM, James Almer wrote: On 5/15/2018 9:49 PM, Peter Bennett wrote: On 05/15/2018 08:44 PM, James Almer wrote: On 5/15/2018 9:25 PM, Peter Bennett wrote: From: Peter Bennett The header stdatomic.h causes compile errors in a c++ compiler, even when

Re: [FFmpeg-devel] [PATCH v2] hwcontext: Add test for device creation and derivation

On Tue, 2018-05-15 at 23:15 +0100, Mark Thompson wrote: > This uses any devices it can find on the host system - on a system with no > hardware device support or in builds with no support included it will do > nothing and pass. > --- > > It now comes under a new target "fate-hw", which is not run

[FFmpeg-devel] compound literal in public header file

The av_err2str macro in libavutil/error.h use compound literal: #define av_err2str(errnum) \     av_make_error_string((char[AV_ERROR_MAX_STRING_SIZE]){0}, AV_ERROR_MAX_STRING_SIZE, errnum) C++ compiler may not support it or treat the usage as invalid. For example, g++ 5.4 raise an error:

Re: [FFmpeg-devel] [PATCH 1/3] hwcontext: Do not call device_init again when deriving an existing device

On 15/05/18 01:42, myp...@gmail.com wrote: > 2018-05-15 5:58 GMT+08:00 Mark Thompson : >> The change in 309d660775e2b47af6723a0477c4d753bc0c54f4 to call device_init >> when doing derivation missed this case - we should only call it if we >> actually made a new device. >> --- >>

[FFmpeg-devel] [PATCH] avcodec/xwddec: fix palette alpha

Signed-off-by: Marton Balint --- libavcodec/xwddec.c | 2 +- tests/ref/lavf/xwd | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/libavcodec/xwddec.c b/libavcodec/xwddec.c index 8b0845fc01..592c98dd4e 100644 --- a/libavcodec/xwddec.c +++

[FFmpeg-devel] [PATCH] avformat: add skip_estimate_duration_from_pts

From: Aman Gupta For seekable mpegts streams, duration is calculated from pts by seeking to the end of the file for a pts and subtracting the initial pts to compute a duration. This can be expensive in terms of added latency during probe, especially when streaming over a network.

Re: [FFmpeg-devel] [PATCH v2] avformat/mpegts: add merge_pmt_versions option

On Tue, May 15, 2018 at 12:23 PM, Aman Gupta wrote: > From: Aman Gupta > > This new optional flag makes it easier to deal with mpegts > samples where the PMT is updated and elementary streams move > to different PIDs in the middle of playback. > > Previously, new

Re: [FFmpeg-devel] [PATCH] avutil/hwcontext_cuda: fix YUV420P cuda_get_buffer

On Tue, 15 May 2018, Timo Rothenpieler wrote: On 15.05.2018 13:37, Marton Balint wrote: Are you sure it isn't already that way? I tested specially YUV420P and could not make out any issues. For 4K content linesize[0] is 3840, but linesize[1] becomes 2048 instead of 1920. That's odd, 2048

Re: [FFmpeg-devel] [PATCH] avformat/webm_chunk: always use a static buffer for get_chunk_filename

On Sun, 13 May 2018, Marton Balint wrote: My conversation from AVFormatContext->filename to AVFormatContext->url was wrong in this case because get_chunk_filename uses filename as an output buffer, and not as an input buffer. Fixes ticket #7188. Pushed and backported. Regards, Marton

Re: [FFmpeg-devel] [PATCH 1/2] avcodec/qtrle: Do not output duplicated frames on insufficient input

2018-05-14 1:07 GMT+02:00, Michael Niedermayer : > Fixes: Timeout > Fixes: > 6383/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_QTRLE_fuzzer-6199846902956032 Looking at the fate change, my suspicion is that the change is a (very) good idea but the commit message could

[FFmpeg-devel] [PATCH] ffprobe: add missing AV_DISPOSITION flags

From: Aman Gupta --- fftools/ffprobe.c | 2 ++ tests/ref/fate/concat-demuxer-extended-lavf-mxf | 2 +- tests/ref/fate/concat-demuxer-extended-lavf-mxf_d10 | 2 +- tests/ref/fate/concat-demuxer-simple1-lavf-mxf| 4

Re: [FFmpeg-devel] [PATCH 1/2] avcodec/qtrle: Do not output duplicated frames on insufficient input

On Tue, May 15, 2018 at 11:02 PM, Michael Niedermayer wrote: > On Mon, May 14, 2018 at 01:31:42AM +0200, Hendrik Leppkes wrote: >> On Mon, May 14, 2018 at 1:07 AM, Michael Niedermayer >> wrote: >> > Fixes: Timeout >> > Fixes: >> >

Re: [FFmpeg-devel] [PATCH 1/2] avcodec/qtrle: Do not output duplicated frames on insufficient input

2018-05-16 0:29 GMT+02:00, Hendrik Leppkes : > It makes no real difference if its less efficient or whatever - > if a codec specification asks for this behavior, then our > decoders should act accordingly. I wonder where this suddenly comes from? (I was away from my mail

Re: [FFmpeg-devel] [PATCH] avcodec: Disable new iterate API for ossfuzz

On Mon, May 14, 2018 at 01:14:01PM +0200, Michael Niedermayer wrote: > A few days ago ossfuzz stoped testing new FFmpeg as it run out of diskspacee > > https://oss-fuzz-build-logs.storage.googleapis.com/index.html > > An alternative would be to revert the API. > > This changes for example >

Re: [FFmpeg-devel] [PATCH 1/2] avcodec/qtrle: Do not output duplicated frames on insufficient input

On Mon, May 14, 2018 at 01:31:42AM +0200, Hendrik Leppkes wrote: > On Mon, May 14, 2018 at 1:07 AM, Michael Niedermayer > wrote: > > Fixes: Timeout > > Fixes: > > 6383/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_QTRLE_fuzzer-6199846902956032 > > > > Found-by:

Re: [FFmpeg-devel] [PATCH v2] configure: error out on unsupported MSVC versions

2018-05-15 6:17 GMT+02:00, Rostislav Pehlivanov : > The FATE tests for MSVC versions older than 2013 are untested in FATE > and apparently are no longer supported. > > This commit makes the configure process error out in case an older version > is used, and suggests to use a