nwchem fails to build with Python 3.10.0a2. make[1]: Entering directory '/builddir/build/BUILD/nwchem-5d4a0e84c8f8d9656a0ac37e796a9a4eff8c5ad9/src/python' /bin/sh: python3.1-config: command not found Compiling python_input.F... /bin/sh: python3.1-config: command not found Compiling task_python.c... task_python.c:4:10: fatal error: Python.h: No such file or directory 4 | #include <Python.h> | ^~~~~~~~~~ compilation terminated. For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.10/fedora-rawhide-x86_64/01783630-nwchem/ For all our attempts to build nwchem with Python 3.10, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.10/package/nwchem/ Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.10: https://copr.fedorainfracloud.org/coprs/g/python/python3.10/ Let us know here if you have any questions. Python 3.10 will be included in Fedora 35. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.10. A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon. We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.
Upstream issue https://github.com/nwchemgit/nwchem/issues/271. Questions: 1. Is python3.10-config available by convention for python development builds, like 3.10.0a2? 2. Is there a way to test python 3.10 directly in a koji scratch build?
1. yes. dnf install python3.10 2. no. only mock/copr
Build succeeded at https://copr.fedorainfracloud.org/coprs/g/python/python3.10/build/1793104/
Thanks.