pkgconf 2.3.0_1 is already installed and up-to-date. To reinstall 2.3.0_1, run: brew reinstall pkgconf

Already linked: /opt/homebrew/Cellar/pkgconf/2.3.0_1

Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.

cmake 3.31.1 is already installed and up-to-date. To reinstall 3.31.1, run: brew reinstall cmake

gettext 0.22.5 is already installed and up-to-date. To reinstall 0.22.5, run: brew reinstall gettext

Already linked: /opt/homebrew/Cellar/gettext/0.22.5

The macOS-12 environment is deprecated, consider switching to macOS-13, macOS-14 (macos-latest) or macOS-15. For more details, see https://github.com/actions/runner-images/issues/10721

pkg-config 0.29.2_3 is already installed and up-to-date. To reinstall 0.29.2_3, run: brew reinstall pkg-config

Already linked: /usr/local/Cellar/pkg-config/0.29.2_3

Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.

cmake 3.30.3 is already installed and up-to-date. To reinstall 3.30.3, run: brew reinstall cmake

docbook-xsl 1.79.2_1 is already installed and up-to-date. To reinstall 1.79.2_1, run: brew reinstall docbook-xsl

gettext 0.22.5 is already installed and up-to-date. To reinstall 0.22.5, run: brew reinstall gettext

imagemagick 7.1.1-38_2 is already installed and up-to-date. To reinstall 7.1.1-38_2, run: brew reinstall imagemagick

You are using macOS 12. We (and Apple) do not provide support for this old version. It is expected behaviour that some formulae will fail to build in this old version. It is expected behaviour that Homebrew will be buggy and slow. Do not create any issues about this on Homebrew's GitHub repositories. Do not create any issues even if you think this message is unrelated. Any opened issues will be immediately closed without response. Do not ask for help from Homebrew or its maintainers on social media. You may ask for help in Homebrew's discussions but are unlikely to receive a response. Try to figure out the problem yourself and submit a fix as a pull request. We will review it but may or may not accept it.