https://bugzilla.redhat.com/show_bug.cgi?id=2223039
--- Comment #7 from Dan Horák dan@danny.cz --- IMO there is something wrong with how the rpm is built. First it builds unicorn, the lib, samples, etc. and all goes well. Then it goes for the python bindings and here the python script builds unicorn for the second time and things go bad. I believe the python bindings should just use the unicorn library built in the first step, probably via the prebuilt subdir and some symlinks. In the current rpms (for all arches) both unicorn and python3-unicorn rpms provide the libunicorn.so.2 file (the python3 subpackage even contains libunicorn.a). This sounds wrong ...
I suppose the "python" version of unicorn is built with some different cmake options (setup.py calls cmake) or something like that.