WIP BROKEN libticonv, libtifiles, libticables, libticalcs: attempt to… #116
Annotations
1 error and 10 warnings
|
Build tilibs
Process completed with exit code 1.
|
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Install dependencies
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.
|
|
Install dependencies
cmake 3.30.3 is already installed and up-to-date.
To reinstall 3.30.3, run:
brew reinstall cmake
|
|
Install dependencies
ninja 1.12.1 is already installed and up-to-date.
To reinstall 1.12.1, run:
brew reinstall ninja
|
|
Install dependencies
gettext 0.22.5 is already installed and up-to-date.
To reinstall 0.22.5, run:
brew reinstall gettext
|
|
Install dependencies
libarchive 3.7.6 is already installed and up-to-date.
To reinstall 3.7.6, run:
brew reinstall libarchive
|
|
Install dependencies
glib 2.82.1 is already installed and up-to-date.
To reinstall 2.82.1, run:
brew reinstall glib
|
|
Install dependencies
libusb 1.0.27 is already installed and up-to-date.
To reinstall 1.0.27, run:
brew reinstall libusb
|
|
Install dependencies
zlib 1.3.1 is already installed and up-to-date.
To reinstall 1.3.1, run:
brew reinstall zlib
|
|
Install dependencies
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.
|
Loading