On 02. 02. 21 14:35, Richard Shaw wrote:
I'm updating OpenImageIO to the latest version and usually simple version bumps
and rebuilds work just fine, so I was surprised when the build failed...
RPM build errors:
error: File not found:
/builddir/build/BUILDROOT/OpenImageIO-2.2.11.1-1.fc34.x86_64/usr/lib64/python3.9/site-packages/OpenImageIO.so
Which literally has been fine a month ago...
As it turns out the library name changed to:
/usr/lib64/python3.9/site-packages/OpenImageIO.cpython-39-x86_64-linux-gnu.so
<http://OpenImageIO.cpython-39-x86_64-linux-gnu.so>
Am I just supposed to glob this in my spec file or is there a macro which will
generate the correct output?
$ rpm --eval '%{python3_ext_suffix}'
.cpython-39-x86_64-linux-gnu.so
I'm venting and I know it's not safe, but I'm a$$uming that upstream didn't
change anything causing this. What I need is predictability so I don't have to
fix stupid stuff. I've got enough to do with failures related to the mass rebuild.
I don't know *what* has changed but it was not Python.
If you build the extension with Python native tooling
(setuptools/distutils/etc.) you always get the more complex suffix.
It is usually cmake/autotools/etc. scripts that build the extension with the
simpler .so suffix.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
