Opened 3 years ago

Last modified 3 years ago

#63345 closed defect

openjdk16-temurin @16.0.2_0: libjli.dylib code signature invalid after upgrading to new openjdk16-temerin — at Initial Version

Reported by: JD-Veiga Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.7.1
Keywords: Cc: nils@…
Port: openjdk16-temurin

Description

Hi,

I have been experienced difficulties with Java after upgrading openjdk16 to version 16.0.2 (which adds port openjdk16-temurin).

When I try to run Eclipse from terminal, I got the following message:

Error loading /Library/Java/JavaVirtualMachines/openjdk16-temurin/Contents/MacOS/libjli.dylib:  dlopen(/Library/Java/JavaVirtualMachines/openjdk16-temurin/Contents/MacOS/libjli.dylib, 265): no suitable image found.  Did find:
	/Library/Java/JavaVirtualMachines/openjdk16-temurin/Contents/MacOS/libjli.dylib: code signature invalid for '/Library/Java/JavaVirtualMachines/openjdk16-temurin/Contents/MacOS/libjli.dylib'

Conversely, when I ran Eclipse from its icon (app), I got a different message:

Error loading /Library/Java/JavaVirtualMachines/openjdk16-temurin/Contents/MacOS/libjli.dylib:  dlopen(/Library/Java/JavaVirtualMachines/openjdk16-temurin/Contents/MacOS/libjli.dylib, 265): no suitable image found.  Did find:
	/Library/Java/JavaVirtualMachines/openjdk16-temurin/Contents/MacOS/libjli.dylib: code signature invalid for '/Library/Java/JavaVirtualMachines/openjdk16-temurin/Contents/MacOS/libjli.dylib'

However, I think that the ultimate cause could be that libjli.dylib is not properly signed.

Whatever the cause, both libjli.dylib and libjvm.dylib exist in their corresponding directories.

I am running:

  • macos Mojave 10.14.6
  • MacPorts 2.7.1

Thanks a lot.

Change History (0)

Note: See TracTickets for help on using tickets.