On 11/09/2015 12:55 AM, Alan Bateman wrote:
On 08/11/2015 17:51, Jan Lahoda wrote:
Automatic modules depend on all other named modules, and javac
currently uses all modules it knows about, which includes those it
found while analyzing other module-infos. I think it could be changed
to
On 08/11/2015 09:56, Florian Troßbach wrote:
:
I did some more “research" about the OSX build though, and i found
this:
https://www.mail-archive.com/build-dev@openjdk.java.net/msg15343.html.
This prompted me to replace the offending sections
from /hotspot/make/bsd/makefiles/gcc.make (around
Hi Alan,
Thank you for your answer, building the JDK myself this error goes away.
Building my own JDK was not without challenges on OSX Mavericks though:
I first mistakenly cloned the wrong repository (the JDK9 without Jigsaw. It
compiled just fine, but I of course discovered my error when javac
On 7.11.2015 15:34, Alan Bateman wrote:
On 07/11/2015 10:15, Florian Troßbach wrote:
:
When I compile my modules with
javac -d . -mp ../jars -modulesourcepath . -verbose $(find . -name
"*.java")
I get the attached output. The raised error is "error: cannot find
module:
On 07/11/2015 10:15, Florian Troßbach wrote:
:
When I compile my modules with
javac -d . -mp ../jars -modulesourcepath . -verbose $(find . -name
"*.java")
I get the attached output. The raised error is "error: cannot find module:
jdk.management.resource”.
This is a bug in the EA build
