Avoid compiling llvm from source every time we upgrade brew

[kirk86]

I was wondering if there's a way to avoid compiling llvm from source whenever we execute brew upgrade.
It is so annoying since it takes very very long hours to compile.

Hunk #1 succeeded at 300 (offset -6 lines).
patching file llvm/lib/Support/CMakeLists.txt
Hunk #2 succeeded at 199 (offset -28 lines).
Hunk #3 succeeded at 210 (offset -28 lines).
patching file llvm/lib/WindowsManifest/CMakeLists.txt
patching file llvm/lib/WindowsManifest/WindowsManifestMerger.cpp
patching file llvm/test/CMakeLists.txt
patching file llvm/test/lit.cfg.py
Hunk #1 succeeded at 352 (offset -4 lines).
patching file llvm/test/lit.site.cfg.py.in
patching file llvm/utils/gn/secondary/lld/test/BUILD.gn
patching file llvm/utils/gn/secondary/llvm/include/llvm/Config/BUILD.gn
Hunk #1 succeeded at 302 (offset -2 lines).
patching file llvm/utils/gn/secondary/llvm/test/BUILD.gn
Hunk #1 succeeded at 161 (offset -1 lines).
==> cmake -G Unix Makefiles .. -DLLVM_ENABLE_PROJECTS=clang;clang-tools-extra;lld;lldb;polly;openmp -DLLVM_ENABLE_RUNTIMES=compiler-rt;libcxx;libcxxabi;libunw
==> make

Is there any solution around this?

[SMillerDev]

Without knowing anything about your configuration I can't debug this (brew doctor and brew config). But the vast majority of homebrew users doesn't compile anything because we provide prebuilt binaries (bottles) that are just moved to the right directory in the system.

[kirk86]

brew config
HOMEBREW_VERSION: 2.5.1-44-g9dd5d42-dirty
ORIGIN: https://github.com/Homebrew/brew
HEAD: 9dd5d42477f66ed0a61557f626799461a8ae7003
Last commit: 6 weeks ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: eb08cfdf699c281c8bfc1a9aa7db41a5dc39f415
Core tap last commit: 6 hours ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: /private/tmp/com.apple.launchd.YR0TIkggQ5/org.macosforge.xquartz:0
HOMEBREW_MAKE_JOBS: 4
HOMEBREW_NO_ANALYTICS: set
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: quad-core 64-bit broadwell
Clang: 12.0 build 1200
Git: 2.24.3 => /Applications/IDE/Xcode.app/Contents/Developer/usr/bin/git
Curl: 7.64.1 => /usr/bin/curl
Java: 14.0.2, 1.8.0_92
macOS: 10.15.7-x86_64
CLT: 12.0.26.2
Xcode: 12.1 => /Applications/IDE/Xcode.app/Contents/Developer
XQuartz: 2.7.11 => /opt/X11

brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Some installed formulae were deleted!
You should find replacements for the following formulae:
  python@2
  mongodb
  libiomp

Warning: "config" scripts exist outside your system or Homebrew directories.
`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and which additional flags to use when
compiling and linking.

Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew-provided
script of the same name. We found the following "config" scripts:
  /Users/jm/miniconda3/bin/python3.7-config
  /Users/jm/miniconda3/bin/python3.7m-config
  /Users/jm/miniconda3/bin/python3-config
  /Users/jm/miniconda3/bin/ncursesw6-config

Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected dylibs:
  /usr/local/lib/libnnz11.dylib
  /usr/local/lib/libociei.dylib
  /usr/local/lib/libocijdbc11.dylib

Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
  python@2
  [email protected]
Error: unknown or unsupported macOS version: :mountain_lion

[SMillerDev]

You seem to be intentionally on an older version of brew, what did you change in there?

[kirk86]

I don't understand how that might have happened since I'm operating under the impression that brew upgrade would have also updated brew alongside any installed packages.

But for sure I was trying intentionally trying to operate on older brew version and I haven't changed anything as far I know, what would make you think that?

Is there any solution here?

[jonchang]

Run brew update-reset

[SMillerDev]

But for sure I was trying intentionally trying to operate on older brew version and I haven't changed anything as far I know, what would make you think that?

HOMEBREW_VERSION: 2.5.1-44-g9dd5d42-dirty would suggest you have local changes in the brew directory. They might be accidental, but usually they aren't.