Aurora

Apparently the Travis template will also need updating, as it isn't aware of C++17

Currently encountering an issue with `operator+` for type conversion between basic string & basic string view. ``` ./lat/arctic-weight.h:52:59: error: no match for ‘operator+’ (operand types are ‘std::string’ {aka ‘std::__cxx11::basic_string’} and...

> The tricky thing, and the reason we hvaen't done this earlier, is that we don't want to break existing builds with older OpenFST versions. I assume OpenFST must export...

Noting that this PR also pertains to https://github.com/kaldi-asr/kaldi/issues/4131 and https://github.com/kaldi-asr/kaldi/issues/4393

> Ad the C++17 Lots of the OpenFST stuff is templated and now written with the C++17 features, so I'm afraid you will need C++17 compliant compiler every time you...

Daniel Povey ***@***.***> writes: > I wonder whether, if it's not practical to make everything conditional, we could create a separate branch of Kaldi for use with the more recent...

Yuriy Chernyshov ***@***.***> writes: > @auroraanon38, is there some work still going on in this issue? > We have some patches that fix compatibility with newer versions of OpenFST. Nope,...

mtdcr ***@***.***> writes: > Since the original issue was triggered by Xorg, likely with Intel GPUs, I looked up which driver I'm using and it's not the default one. Maybe...

mtdcr ***@***.***> writes: >> ``` >> Section "Device" >> Identifier "Intel Graphics" >> Driver "intel" >> Option "TearFree" "true" >> EndSection >> ``` > > Removing this section made the...