[MacPorts] #73975: openjdk11 @11.0.31_0+release+server broken linking after rebuilding

MacPorts noreply at macports.org
Tue May 5 22:16:54 UTC 2026


#73975: openjdk11 @11.0.31_0+release+server broken linking after rebuilding
------------------------+----------------------
  Reporter:  dbl001     |      Owner:  breun
      Type:  defect     |     Status:  assigned
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.12.5
Resolution:             |   Keywords:
      Port:  openjdk11  |
------------------------+----------------------

Comment (by breun):

 I see that you're running macOS 10.15 and I'm afraid the current set of
 OpenJDK updates (11.0.31, 17.0.19, 21.0.11, 25.0.3) all need macOS 11 or
 later to build and run. Support for macOS 10.15 and older has been dropped
 by the OpenJDK project.

 The last OpenJDK versions that build and run on macOS 10.15 were 11.0.30,
 17.0.18, 21.0.10 and 25.0.2, but these versions contain
 [https://openjdk.org/groups/vulnerability/advisories/2026-04-21 known
 security issues]) (and more issues that affect these older versions may be
 discovered in the future), which is why I'm not too keen to provide these
 outdated versions via MacPorts.

 Do you need the `openjdk11` port to satisfy a dependency for another port?
 If you don't need it as a dependency for another port, but you need a JDK
 to build or run some software outside MacPorts, I recommend uninstalling
 the `openjdk11` port and downloading a binary .tar.gz distribution of
 OpenJDK 11.0.30, like
 [https://github.com/adoptium/temurin11-binaries/releases/tag/jdk-11.0.30%2B7
 Eclipse Temurin] or
 [https://www.azul.com/downloads/?version=java-11-lts&os=macos&package=jdk
 &show-old-builds=true#zulu Azul Zulu], unpacking that in a directory under
 `/Library/Java/JavaVirtualMachines` and updating your `JAVA_HOME`
 environment variable if applicable. Note that version 11.0.30 of these
 binary distributions will also contain the security issues that affect
 OpenJDK 11.0.30.

 If you do need `openjdk11` as a dependency for another port, the only
 thing I could do is letting the port install an outdated version on macOS
 <11.

-- 
Ticket URL: <https://trac.macports.org/ticket/73975#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list