Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8238225

Issues reported after replacing symlink at Contents/MacOS/libjli.dylib with binary

    XMLWordPrintable

Details

    • b27
    • 14
    • b09
    • os_x

    Backports

      Description

        JDK-8235687 replaced the symlink for Contents/MacOS/libjli.dylib, pointing to MacOS/Home/lib/libjli.dylib resp. MacOS/Home/lib/jli/libjli.dylib. It seems to cause problems.

        One problem reported is when trying to launch Eclipse IDE bundles. The VM cannot be created when using the new bundle structure.

        There was also a case reported where the customer has a custom launcher that uses CFBundleLoadExecutableAndReturnError and CFBundleGetFunctionPointerForName for resolving and invoking "JNI_CreateJavaVM".

        It is also unclear whether Apple really requires a symlink-free bundle for notarization. Up to now I got reports that people could notarize bundles with symlink, still.

        If the symlink requirement will definitely be enforced, I assume libjli must be fixed to be able to handle the new MacOS bundle structure.

        Attachments

          Issue Links

            Activity

              People

                erikj Erik Joelsson
                clanger Christoph Langer
                Votes:
                0 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: