https://bugzilla.redhat.com/show_bug.cgi?id=1791588
--- Comment #2 from Luya Tshimbalanga <luya_tfz(a)thefinalzone.net> ---
Look at the failure of compiling, it appears the issue occured on that line:
/usr/bin/ld: ./.libs/libvapoursynth-script.so: undefined reference to
`Py_InitializeEx'
/usr/bin/ld: ./.libs/libvapoursynth-script.so: undefined reference to
`PyDict_GetItemString'
/usr/bin/ld: ./.libs/libvapoursynth-script.so: undefined reference to
`PyObject_GetAttrString'
/usr/bin/ld: ./.libs/libvapoursynth-script.so: undefined reference to
`_Py_Dealloc'
/usr/bin/ld: ./.libs/libvapoursynth-script.so: undefined reference to
`PyImport_ImportModule'
/usr/bin/ld: ./.libs/libvapoursynth-script.so: undefined reference to
`PyCapsule_GetPointer'
/usr/bin/ld: ./.libs/libvapoursynth-script.so: undefined reference to
`PyCapsule_IsValid'
/usr/bin/ld: ./.libs/libvapoursynth-script.so: undefined reference to
`PyEval_SaveThread'
/usr/bin/ld: ./.libs/libvapoursynth-script.so: undefined reference to
`PyGILState_Ensure'
/usr/bin/ld: ./.libs/libvapoursynth-script.so: undefined reference to
`Py_IsInitialized'
collect2: error: ld returned 1 exit status
make: *** [Makefile:1324: vspipe] Error 1
Similar report from upstream suggests a python3 issue:
https://github.com/vapoursynth/vapoursynth/issues/518
And possible workaround:
https://docs.python.org/3/whatsnew/3.8.html#debug-build-uses-the-same-abi...
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component