Most interesting here: There are placeholders for
pointers and
strings in a format string which are not interpreted as if preceded by a %. I would suspect issues with string functions.
Where did you get these x265 builds from, which compiler did they use? (e.g. run "x265 -V" in a console, that should reveal used compilers, or additional format string failures)
There was a patch
e2759ae:
Quote:
dhdr: Replace the header "string" with its C++ equivalent <cstring> to fix build failures.
|
It looks a bit compiler dependent to me. But I am no expert regarding C++ compilers...