![]() # change the name of the formula by removing "AT682" from the `class` definition # `extract` the version you'd like to install into a custom tapĬd $(brew -repository $USER/local-tap)/Formula If you don’t want to go that route, here’s the easiest alternative I found: # uninstall the newer version of the package that you accidentally installedīrew uninstall -ignore-dependencies icu4c The downside with this approach is if you aren’t installing the package directly you’d have to modify the underlying script which could be a major pain. Now, the preferred way to switch versions is to relink a specific version: brew link -overwrite -force this doesn’t work: Warning: Refusing to link macOS provided/shadowed software: you need to have icu4c first in your PATH, run:įor compilers to find icu4c you may need to set:Įxport pkg-config to find icu4c you may need to set:Įxport what I can tell, the only real workaround for this error is to manually specify the environment variables indicated in the installation post-install message. If it wasn’t for this nuance, this StackOverflow answer would have had all of the information I needed.Īdditionally, even if the package name was the same, brew removed the switch command. The package name is with version 68.2 which means any scripts which check for a package via brew list -version icu4c will fail. ![]() However, extracting a specific version through this method does not use the same package name. Instead of something like brew install you need to execute (found this snippet through this blog post): brew tap-new $USER/local-tapīrew extract -version=68.2 icu4c $USER/local-tapīrew install can determine the last supported version in homebrew using git history via the URL exposed when running brew info icu4c. Unfortunately, this method of installation was removed in a recent version of brew. Make: *** Error 1īrew used to support installing packages via a formula URL. make emitted an error with an ‘international’ ( intl) identifier in the offending file, which after some googling indicated that icu4c was the offending package: 3 errors generated. I discovered the offending package was icu4c, but the PHP compile script did not indicate that I was using an unsupported package version. I ended up learning a bit about the homebrew internals and solving Installing an old version of icu4c to fix PHP compilation on macOS I thought it would be easy to install an older version of the offending package, icu4c, but I was very wrong. This caused issues compiling PHP via asdf. I accidentally ran brew upgrade on a set of packages which caused brew to bump most library packages that were installed on my computer.
0 Comments
Leave a Reply. |