23.04.2020, 22:36
Sure, I closed and reopened the terminal. I even tried to reboot and ran vspipe --version after that. Still no success. I checked the mvtools.log in build/log directory, bud didn't find anything suspicious. But I could miss something.
If I remove libmvtools.so from /usr/local/lib/vapoursynth directory, vspipe --version runs well! But I expect Vapoursynth won't work in that case. Maybe the better way would be to avoid building mvtools at all. But I don't have idea what consequences this would have.
One thing is clear, libmvtools.so is somehow broken after build in Ubuntu 18.04. Is there any way how to solve that?
If I remove libmvtools.so from /usr/local/lib/vapoursynth directory, vspipe --version runs well! But I expect Vapoursynth won't work in that case. Maybe the better way would be to avoid building mvtools at all. But I don't have idea what consequences this would have.
One thing is clear, libmvtools.so is somehow broken after build in Ubuntu 18.04. Is there any way how to solve that?