Skip to content

Bring back string early return, remove header #20

Bring back string early return, remove header

Bring back string early return, remove header #20

Triggered via push October 4, 2024 02:32
Status Failure
Total duration 20m 55s
Artifacts

macos.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 10 warnings
build
The `brew link` step did not complete successfully
build
Process completed with exit code 1.
build
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.
build
gettext 0.22.5 is already installed and up-to-date. To reinstall 0.22.5, run: brew reinstall gettext
build
freetype 2.13.3 is already installed and up-to-date. To reinstall 2.13.3, run: brew reinstall freetype
build
gmp 6.3.0 is already installed and up-to-date. To reinstall 6.3.0, run: brew reinstall gmp
build
jpeg-turbo 3.0.4 is already installed and up-to-date. To reinstall 3.0.4, run: brew reinstall jpeg-turbo
build
libogg 1.3.5 is already installed and up-to-date. To reinstall 1.3.5, run: brew reinstall libogg
build
libpng 1.6.44 is already installed and up-to-date. To reinstall 1.6.44, run: brew reinstall libpng
build
libvorbis 1.3.7 is already installed and up-to-date. To reinstall 1.3.7, run: brew reinstall libvorbis
build
zstd 1.5.6 is already installed and up-to-date. To reinstall 1.5.6, run: brew reinstall zstd
build
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.