jdk10 on macOS

Jonathan Gibbons jonathan.gibbons at oracle.com
Fri Jan 5 21:45:48 UTC 2018


1. The build labelled jtreg-4.2.0-tip.tar.gz should work for you.
     https://ci.adoptopenjdk.net/view/Dependencies/job/jtreg/

2. The build instructions are here:
     http://openjdk.java.net/jtreg/build.html
     See the section on using the "build-all.sh" script.

-- Jon

On 01/05/2018 01:35 PM, Alan Snyder wrote:
> Maybe not as easy as you expect:
>
> ant -f make/build.xml
> Buildfile: /Volumes/A/JDK/jtreg/make/build.xml
>
> -init:
>
> import-javahelp:
>
> BUILD FAILED
> /Volumes/A/JDK/jtreg/make/build.xml:246: Warning: Could not find file 
> /opt/javahelp/2.0/javahelp/lib/jh.jar to copy.
>
>
>
> make -C make
>
>>
> ../src/share/classes/com/sun/javatest/regtest/agent/TestNGRunner.java:33: 
> error: package org.testng does not exist
>
> ...
>
>
>> On Jan 5, 2018, at 1:02 PM, Jonathan Gibbons 
>> <jonathan.gibbons at oracle.com <mailto:jonathan.gibbons at oracle.com>> wrote:
>>
>> Alan,
>>
>> I confirm there are problems with the jtreg builds from the Adopt 
>> OpenJDK group. I'll investigate what we can do to fix this.
>>
>> -- Jon
>>
>> On 01/05/2018 12:36 PM, Jonathan Gibbons wrote:
>>> That sounds like a problem using an older build of jtreg, from the 
>>> Adopt OpenJDK group. The tell-tale evidence is the Class-Path entry 
>>> in the jtreg.jar MANIFEST.MF file:  does that entry include 
>>> asmtools.jar?
>>>
>>> There have been build changes for jtreg recently, that should have 
>>> addressed this problem. If nothing else, it is now much easier to 
>>> build jtreg yourself. The only external components you need are Ant 
>>> and a recent JDK, such as JDK 8. Everything else will be downloaded, 
>>> and built if necessary.
>>>
>>> -- Jon
>>>
>>>
>>> On 1/5/18 12:21 PM, Alan Snyder wrote:
>>>> I am trying to build jdk10 on macOS 10.12.6. I got the basic build 
>>>> to work, but some tests fail.
>>>>
>>>> Most of the test failures complain about not finding jasm or 
>>>> jcoder. This is odd because I downloaded jtreg-4.2-b11, which 
>>>> includes these classes, and the classpath appears to be correct in 
>>>> the log.
>>>>
>>>> I got an error from StringPlatformChars, which could find native 
>>>> code. Could be the same jasm problem but not reported as such.
>>>>
>>>> I got an error from NewUnsafeString, did not use provided string.
>>>>
>>>
>>
>



More information about the build-dev mailing list