New builds will get a checksum file via
2fc2ab6cf0
and stale checksum files of old builds have been removed in the previous commit.
So this change does not lead to any diff in the rendering at this point.
Except for mingw-w64-qt5-serialbus* which was built after
2fc2ab6cf0
none of these packages have a checksum anymore (as they use VCS sources after
switching to the KDE fork version).
This commit removes the stale checksum files as they are probably confusing.
This was done via:
```
for p in qt5-* ; do source $p/mingw-w64/PKGBUILD ; [[ ${sha256sums[0]} == SKIP ]] && rm -v $p/*/*-sha256.txt ; done
```
Add patch to mingw-w64-gcc after updating to 14.1.1 to fix build errors
like:
```
<built-in>: error: conflicting declaration of C function ‘int __cxxabiv1::__cxa_thread_atexit(void (*)(), void*, void*)’
In file included from /home/devel/.cache/aurman/mingw-w64-paraview/src/ParaView-v5.12.0/build-x86_64-w64-mingw32/VTK/Common/Core/vtkCxxABIConfigure.h:10,
from /home/devel/.cache/aurman/mingw-w64-paraview/src/ParaView-v5.12.0/VTK/Common/Core/vtkTypeName.h:7,
from /home/devel/.cache/aurman/mingw-w64-paraview/src/ParaView-v5.12.0/VTK/Common/DataModel/vtkCellGrid.h:28:
/usr/x86_64-w64-mingw32/include/c++/14.1.1/cxxabi.h:140:3: note: previous declaration ‘int __cxxabiv1::__cxa_thread_atexit(void (*)(void*), void*, void*)’
140 | __cxa_thread_atexit(void (_GLIBCXX_CDTOR_CALLABI *)(void*), void*, void *) _GLIBCXX_NOTHROW;
```
* Use `git+https://sourceware.org/git/gcc.git` consistently in both
packages
* Remove ada from static-compat-gcc because it leads to build failures and
adding even more workarounds for this language is not worth it
* Workaround certain warnings now being treated as errors in mingw-w64-gcc
The switch to Qt 6 is required for the ICU 75 rebuild because only when using
Qt 6 the build system uses C++ 17 which is required as of ICU 75.
Unfortunately it doesn't build against Qt 6 / KF6 yet so I'm dropping it from
the binary repo for now.
* Set consistent Android API level
* Ensure make utilizes all CPU cores if `MAKEFLAGS` are otherwise cleared
via `!buildflags` because this is nevertheless wanted in mingw-w64 and
android packages (that usually set `!buildflags`)
* Ensure required devel packages are installed
Martchus
Raffaele Mancuso
Wolfgang Pupp
Gonzalo Exequiel Pedone