Hello Clausi_e,
When I did search for py_initmodule4 I stumbled on this text in a result:
Apparently on 64-bit linux, in libpython2.[56].so, the symbol is renamed to Py_InitModule4_64.
I still build with a 32-bit Linux and realise that these are becoming outdated more and more. The reason for doing this is that the SH4 environment is 32 bit, and especially with python you need to compile the SH4 parts on a machine having the same python version installed as you are using on the receiver. As somebody has had the wisdom to use different symbol names for the same thing on 32- and 64-bit environments, this may well explain your problem if you are using a 64-bit Linux as your OS.
It may therefore well be that my build succeeds because I am building on Linux Mint 18.3 32-bit, thus avoiding this puzzle by accident. In the past I have had several problems with building on 64-bit machines, and since then I have stuck with 32-bit to avoid them. As stated more and more distributions are only offering 64-bits versions, so in the future a solution for this puzzle must be found, although it may also be possible that the problem will solve itself when OpenPLi finally switches to Python3, as Python is now more than a year end-of-life.
Regards,
Audioniek.