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

Conflicting jpackage static library name

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 17, 18
    • Fix Version/s: 18
    • Component/s: tools
    • Labels:
    • Subcomponent:
    • Resolved In Build:
      b26
    • OS:
      linux

      Description

      When building bundles, and in particular the static-libs bundle, on linux, make spits out the following:

      StaticLibsImage.gmk:41: warning: overriding recipe for target 'build/linux-x64/images/static-libs/lib/libjpackageapplauncher.a'
      StaticLibsImage.gmk:41: warning: ignoring old recipe for target 'build/linux-x64/images/static-libs/lib/libjpackageapplauncher.a'

      The reason seems to boil down to the two different artifacts defined in make/modules/jdk.jpackage/Lib.gmk: BUILD_JPACKAGE_APPLAUNCHEREXE and the linux specific BUILD_JPACKAGE_LIBAPPLAUNCHER.

      Both of them end up defining a static library with the same base name - libjpackageapplauncher.a. The static-libs bundling logic assumes that all static library names are unique and flattens the paths when preparing to bundle up the static libraries, meaning it ends up trying to define two different (CopyFiles) recipes for the same target path:

      build/linux-x64-release/images/static-libs/lib/libjpackageapplauncher.a

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              asemenyuk Alexey Semenyuk
              Reporter:
              mikael Mikael Vidstedt
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: