Looks good. igor
> On Mar 6, 2017, at 2:40 PM, Vladimir Kozlov <vladimir.koz...@oracle.com> > wrote: > > Webrev: > http://cr.openjdk.java.net/~kvn/8176238/webrev/ > >> On 3/6/17 2:31 PM, Vladimir Kozlov wrote: >> https://bugs.openjdk.java.net/browse/JDK-8176238 >> >> jdk.internal.vm.compiler build fails when --with-jobs=1 is used by >> configure. Mandy suggested to add --add-modules jdk.internal.vm.ci to >> Graal annotation process command line to avoid the problem: >> >> diff -r 932b4ec7397f make/gensrc/Gensrc-jdk.internal.vm.compiler.gmk >> --- a/make/gensrc/Gensrc-jdk.internal.vm.compiler.gmk >> +++ b/make/gensrc/Gensrc-jdk.internal.vm.compiler.gmk >> @@ -81,6 +81,7 @@ >> PROCESSOR_PATH := $(call PathList, $(PROCESSOR_JARS)) >> >> ADD_EXPORTS := \ >> + --add-modules jdk.internal.vm.ci \ >> --add-exports jdk.internal.vm.ci/jdk.vm.ci.aarch64=ALL-UNNAMED \ >> --add-exports jdk.internal.vm.ci/jdk.vm.ci.amd64=ALL-UNNAMED \ >> --add-exports jdk.internal.vm.ci/jdk.vm.ci.code=ALL-UNNAMED \ >> >> It works but I don't know why this happens only with --with-jobs=1. >> >> Thanks, >> Vladimir