[MacPorts] #61445: Java version not detected on macOS Big Sur 11.0.1
MacPorts
noreply at macports.org
Sat Nov 28 02:06:15 UTC 2020
#61445: Java version not detected on macOS Big Sur 11.0.1
---------------------+--------------------
Reporter: breun | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: |
---------------------+--------------------
Comment (by catap):
I've discovered that `-f` is a cause for strange behaviour:
{{{
catap at Kirills-mini-m1 ~ % env | grep JAVA
catap at Kirills-mini-m1 ~ % /usr/libexec/java_home -V
Matching Java Virtual Machines (2):
16 (arm64) "Azul Systems, Inc." - "Zulu 16.0.65-ea"
/Library/Java/JavaVirtualMachines/zulu-jdk16/Contents/Home
11.0.9.1 (arm64) "Azul Systems, Inc." - "Zulu 11.43.1007"
/Library/Java/JavaVirtualMachines/zulu-jdk11/Contents/Home
/Library/Java/JavaVirtualMachines/zulu-jdk16/Contents/Home
catap at Kirills-mini-m1 ~ % /usr/libexec/java_home -v 1.8+
/Library/Java/JavaVirtualMachines/zulu-jdk16/Contents/Home
catap at Kirills-mini-m1 ~ % /usr/libexec/java_home -f -v 1.8+
The operation couldn’t be completed. Unable to locate a Java Runtime that
supports (null).
Please visit http://www.java.com for information on installing Java.
catap at Kirills-mini-m1 ~ %
}}}
I have no idea that `-f` means because I haven't found it inside man page
for `java_home` for mac OS Catalina and Big Sur.
=> I've opened PR: https://github.com/macports/macports-ports/pull/9264
that solved issue on two machines with Big Sur.
--
Ticket URL: <https://trac.macports.org/ticket/61445#comment:15>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list