before libc++ was split off from clang package, it was built after clang within the same PKGBUILD, so this order seems reasonably safe.
Also remove a couple of prior cycle breaks from before it was possible to break them manually in a run. These packages are not related by the same source repo and release, like mingw-w64 and llvm-project are, so are less likely to consistently require a cycle break on every upstream update.
before libc++ was split off from clang package, it was built after clang within the same PKGBUILD, so this order seems reasonably safe.
Also remove a couple of prior cycle breaks from before it was possible to break them manually in a run. These packages are not related by the same source repo and release, like mingw-w64 and llvm-project are, so are less likely to consistently require a cycle break on every upstream update.