We went through this exercise in January.
RE intentionally uses what is the documented minimum gnumake (3.81), to
verify that builds work with the oldest supported gnumake.
On 2015/1/31 4:01, David Katleman wrote:
You need to revert your 4.0 change make to JDK9 builds. Until dev
upgrades the minimum gnumake used in the JDK 9 builds to 4.0, RE must
continue to build with the current official minimum, which is 3.81, to
catch that the official minimum still works, as in JDK-8071651
<https://bugs.openjdk.java.net/browse/JDK-8071651>.
I've opened up a high priority enhancement request to get the official
gnumake updated, JDK-8072023
<https://bugs.openjdk.java.net/browse/JDK-8072023>.
Until we update gnumake for windows (JDK-8072023
<https://bugs.openjdk.java.net/browse/JDK-8072023>), issues like what
Phil found with gnumake 3.81 should be fixed.
Thanks
Dave
On 4/14/2015 3:42 PM, Phil Race wrote:
What happens if you do "make java.xml.bind-java"?
Update: This *apparently* succeeded (ie it didn't say it had failed)
but it did not create the "batch" file.
And that is why the subsequent "jdk.xml.bind" target did not succeed.
After some exploration I found I was picking up an older version of
cygwin make (3.81).
Updating my path to pick up a newer cygwin version (4.1) it went
smoothly.
Maybe the README-builds.html should not say "Any GNU make 3.81 or newer"
-phil.
On 4/14/2015 10:41 AM, Phil Race wrote:
On 4/12/2015 11:34 PM, Erik Joelsson wrote:
That looks weird. What does your
/cygdrive/c/jdks/jdk9/build/windows-x86-normal-server-release/make-support/module-deps.gmk
look like?
It looks OK to me. I do have these lines :-
DEPS_java.xml.bind := java.compiler java.datatransfer java.base
java.desktop java.logging java.activation java.xml
..
DEPS_jdk.xml.bind := jdk.compiler java.compiler java.xml.bind
java.datatransfer java.base java.desktop java.logging java.activation
java.xml
.. and lots of other similar lines. No obvious errors.
What happens if you do "make java.xml.bind-java"?
sh-4.1$ make java.xml.bind-java
Building target(s) 'java.xml.bind-java' in configuration
'windows-x86-normal-server-release'
Finished building target(s) 'java.xml.bind-java' in configuration
'windows-x86-normal-server-release'
So that part succeeded, but repeating "make" after that results in
the same error I reported in my initial email.
Exactly how did you run make to have this happen?
I typed "make" :-). Running in a cygwin shell that is inside a
cmd.exe shell (not a cygwin window).
Same as I have always done.
-phil.
/Erik
On 2015-04-11 00:39, Phil Race wrote:
For some time (a couple of weeks) I have run into the following
error whenever I try to build on Windows on my system
I've been using forever .. I have worked around it by doing builds
using JPRT but its getting annoying.
Does anyone have a clue what I am doing wrong. This happens on
brand new clean forests etc.
make[3]: *** No rule to make target
`/cygdrive/c/jdks/jdk9/build/windows-x86-normal-server-release/jdk/modules/java.xml.bind/_the.java.xml.bind_batch',
needed by
`/cygdrive/c/jdks/jdk9/build/windows-x86-normal-server-release/jdk/modules/jdk.xml.bind/_the.jdk.xml.bind_batch'.
Stop.
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [jdk.xml.bind-java] Error 1
make[2]: *** Waiting for unfinished jobs....
make[3]: *** No rule to make target
`/cygdrive/c/jdks/jdk9/build/windows-x86-normal-server-release/jdk/modules/java.xml.bind/_the.java.xml.bind_batch',
needed by
`/cygdrive/c/jdks/jdk9/build/windows-x86-normal-server-release/jdk/modules/java.xml.ws/_the.java.xml.ws_batch'.
Stop.
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [java.xml.ws-java] Error 1
-phil.
