Bazel v1.2.0 accidentally no longer runs on macOS High Sierra
See original GitHub issueDescription of the problem:
I am trying to upgrade Bazel to v1.2.0 in this PR, https://github.com/Homebrew/homebrew-core/pull/46983#issuecomment-556462751
The error only happens on highsierra build. And I can totally reproduce in my repo as well.
Uncompressing......Mismatched bazel version. Found '' expected '1.2.0'.
Installing bazel 1.2.0
Downloading bazel installer for bazel 1.2.0
/tmp/bazel-1.2.0-installer.sh: line 1: syntax error near unexpected token `newline'
/tmp/bazel-1.2.0-installer.sh: line 1: `<!DOCTYPE html>'
dyld: lazy symbol binding failed: Symbol not found: ____chkstk_darwin
Referenced from: /Users/xx/.bazel/bin/bazel-real (which was built for Mac OS X 10.15)
Expected in: /usr/lib/libSystem.B.dylib
What operating system are you running Bazel on?
Mac OS highsierra
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (10 by maintainers)
Top Results From Across the Web
Installing Bazel on macOS
Step 1: Install Xcode command line tools; Step 2: Download the Bazel installer; Step 3: Run the installer; Step 4: Set up your...
Read more >How to fix a split Fusion Drive - Apple Support
If your Fusion Drive appears as two drives instead of one in the Finder, it's no longer working as a Fusion Drive. Here's...
Read more >macOS 10.13 High Sierra Compatibility Info
With UAD-2 and Apollo hardware, UAD software v9.4 through v9.14.5 is tested and compatible with macOS High Sierra. LUNA Recording System is not...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
No. Note that we cannot test Bazel on High Sierra though, because we only have enough CI machines to test on one macOS platform. We rely on users reporting regressions to keep our support for that.
@philwo , I tried it on a machine running MacOS-10.13.6 and it worked!