[BUG] Homebrew openjdk@8 installation failure on M1 Macs
See original GitHub issueInformation
- Apktool Version (
apktool -version
) - N/A - Operating System (Mac, Linux, Windows) - macOS 11.2.3, M1 chip
- APK From? (Playstore, ROM, Other) - N/A
Steps to Reproduce
brew install apktool
Output:
$ brew install apktool
==> Downloading https://homebrew.bintray.com/bottles/m4-1.4.18.arm64_big_sur.bottle.1.tar.gz
Already downloaded: /Users/lelandclemmons/Library/Caches/Homebrew/downloads/4b470a01ecb6ff156120cdde7e724d20140ac991221e6de3094b8223e4c33476--m4-1.4.18.arm64_big_sur.bottle.1.tar.gz
==> Downloading https://homebrew.bintray.com/bottles/autoconf-2.71.arm64_big_sur.bottle.tar.gz
Already downloaded: /Users/lelandclemmons/Library/Caches/Homebrew/downloads/cbc5a82447caab8200a340468767d0f652e04f707412b3679a9e0f857f251b05--autoconf-2.71.arm64_big_sur.bottle.tar.gz
==> Downloading https://homebrew.bintray.com/bottles/pkg-config-0.29.2_3.arm64_big_sur.bottle.tar.gz
Already downloaded: /Users/lelandclemmons/Library/Caches/Homebrew/downloads/543cfd61e9f40f8244c8a3cd1ce4966e302327a5d83af48ccd69bc23d773eceb--pkg-config-0.29.2_3.arm64_big_sur.bottle.tar.gz
==> Downloading https://homebrew.bintray.com/bottles/libpng-1.6.37.arm64_big_sur.bottle.tar.gz
Already downloaded: /Users/lelandclemmons/Library/Caches/Homebrew/downloads/6d1358d2e6b4577cc280ddaeabc8477ab68982f2faad020d431a31e53faaff26--libpng-1.6.37.arm64_big_sur.bottle.tar.gz
==> Downloading https://homebrew.bintray.com/bottles/freetype-2.10.4.arm64_big_sur.bottle.tar.gz
Already downloaded: /Users/lelandclemmons/Library/Caches/Homebrew/downloads/acd4c39bf2c08ce6dd74711474e3411292fae2b5db57553d40165231d856bb8a--freetype-2.10.4.arm64_big_sur.bottle.tar.gz
Error: openjdk@8: no bottle available!
You can try to install from source with:
brew install --build-from-source openjdk@8
Please note building from source is unsupported. You will encounter build
failures with some formulae. If you experience any issues please create pull
requests instead of asking for help on Homebrew's GitHub, Twitter or any other
official channels.
From what I can tell, this is because the M1 chip needs it’s own special version of OpenJDK – might be worth documenting in the installation instructions for now: https://ibotpeaches.github.io/Apktool/install/
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Homebrew : Error: openjdk@8: no bottle available
Error: openjdk@8: no bottle available! You can try to install from source with: brew install --build-from-source openjdk@8 Please note building ...
Read more >Installing OpenJDK on M1 Macbook Pro - Sudaraka Jayathilaka
I recently got hold of a M1 MacBook Pro and was faced with the challenge of ... on project reachup-api: Fatal error compiling:...
Read more >Install OpenJDK Java (8/11/17) versions using brew on Mac ...
brew install openjdk@8. Note: OpenJDK 8 is only available for x86_64 architecture, so you will get an error if you are on ARM...
Read more >How can I install java openjdk 8 on High Sierra or newer macOS
Upon running brew cask install adoptopenjdk8. If you get this error. Error: Unknown command ...
Read more >openjdk@8 - Homebrew Formulae
openjdk@8. Install command: brew install openjdk@8. Development kit for the Java programming language. https://openjdk.java.net/. License: GPL-2.0-only.
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 FreeTop 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
Top GitHub Comments
@Leland it’s working on my Mac mini M1 chip
just try download apktool jar file or build project don’t using brew install and install java 14 from oracle site.
it work for me haha
Note that JDK 8 is required for a lot of projects. Substituting a newer JDK may be not an option for many projects.