Clang generates a compiler error against code which gcc treats as a warning. This change disables that error (only for clang) so the build can succeed. The code needs to be fixed (has been raised with the project), but this allows the build to succeed so downstream consumers (e.g. Gramps) can use the package.
Bumped up the package release.
This reverts commit 9eb7cff95c, reversing
changes made to 3af54f0fab. This commit is just to restore the package; next commit will fix errors to build bsddb3 6.2.9 without upgrading.
There is a mismatch between function pointers that leads to a compilation
error with Clang 16. But even if the build with GCC succeeds, it will likely
crash on runtime.
No one complained about this crash so far. So, there might be no users.
See also #17871.
Not supported on Windows
In our stdlib distutils it will end up using rpath, which clang errors out on,
and in upstream distutils there is a PR pending making it a proper error:
https://github.com/pypa/distutils/pull/150
* python3: Update to 3.6.1
The patches starting with 16 are new to fix the build.
Some no longer relevant patches were dropped, the rest is just refreshed.
* Bump pkgrel of all packages containing Python 3 bytecode/extensions.
The package list was generated using:
pkgfile.exe -R mingw64 -r "cpython.*\\.(py[cod]|dll)"
* lensfun: Add cmake to makedepends
* numpy: Don't hardcode the Python version
* blender: rebuild for new Python
* boost: Don't hardcode Python versions; rebuild
* pillow: Don't hardcode Python version; rebuild
* python-dateutil: Don't hardcode Python versions
* sip: Don't hardcode Python versions
* pyqt4: Don't hardcode Python versions; rebuild
* pyqt5: Don't hardcode Python versions; rebuild
* opencv: Update Python3 version in patch
* upgrade some broken packages
* correct some broken urls/checksums
* use secure urls where possible
* update PKGBUILD templates
* remove line-ending whitespace
* minor typos/fixes
Remaining md5sums either didn't download or
didn't pass checksum tests.