![]() I was able to build a JDK that contained the work-in-progress for JEP 411. Wrapping upīack to the question that triggered this interesting journey. You’re most likely building with either a very old Xcode, or the Xcode Command Line Utilities. If you see XCode tool 'metal' neither found in path nor with xcrun On my machine, it took almost three times as long! Troubleshooting Running this test suite probably takes longer than building the JDK itself. ![]() Jtreg:test/hotspot/jtreg:tier1 1702 1702 0 0įinished building target 'run-test-tier1' in configuration 'macosx-x86_64-server-release' It’s just as easy as the previous steps: run make run-test-tier1.Īgain, if all went well, you should see a report like this: = There’s only one way to find out… run the extensive test suite that comes with it! This is all fun and giggles, but will this custom Java build work correctly? OpenJDK 64-Bit Server VM (build 17-internal , mixed mode, sharing) OpenJDK Runtime Environment (build 17-internal ) If all went well, you should see something like this: openjdk version "17-internal" When that is done, you can do a sanity check by issuing. On my 2018 Macbook with an Intel Core i7 CPU and 16 GB of RAM, the process took a little over 30 minutes. Now on to the next step: getting that fresh Java Development Kit!Īfter issuing make images, grab yourself a beverage of choice. * C Compiler: Version 12.0.5 (at /usr/bin/clang) * Toolchain: clang (clang/LLVM from Xcode 12.5) * Boot JDK: openjdk version "16.0.1" OpenJDK Runtime Environment AdoptOpenJDK-16.0.1 9 (build 16.0.1 9) OpenJDK 64-Bit Server VM AdoptOpenJDK-16.0.1 9 (build 16.0.1 9, mixed mode, sharing) (at /Library/Java/JavaVirtualMachines/adoptopenjdk-16.jdk/Contents/Home) * Version string: 17-internal (17-internal) * OpenJDK target: OS: macosx, CPU architecture: x86, address length: 64 * JVM features: server: 'cds compiler1 compiler2 dtrace epsilongc g1gc jfr jni-check jvmci jvmti management nmt parallelgc serialgc services shenandoahgc vm-structs zgc' If all goes well, the script will summarise the configuration for your build, the tools it will use, and the hardware resource that the build will use: Configuration summary: In most cases, it will give you clear instructions if you lack something. This will perform a bunch of sanity checks to see if you have all the necessary tools. with-gtest=/Users/maarten/stuff/googletest The first step is configuring the build: bash configure \ If you want to experiment with features that aren’t done yet, you may want to switch to a different branch, or even add another Git remote that contains the feature.
0 Comments
Leave a Reply. |