http://hg.openjdk.java.net/jigsaw/jake/ - but it was recently synced to jdk9/dev
(as in a few hours ago) and should be effectively the same. With some luck 
there'll
not be much if any difference between them going forward.

/Claes

On 2017-06-17 11:17, Pepper Lebeck-Jobe wrote:
Thanks Gary. That got me unblocked. One more question about the repository
layout. If I want to be on the bleeding edge of development for the JPMS
(a.k.a Jigsaw) which of these should I be building from?

http://hg.openjdk.java.net/jigsaw/jake/
http://hg.openjdk.java.net/jdk9/jdk9/
http://hg.openjdk.java.net/jdk9/dev

Thanks,
Pepper

On Sat, Jun 17, 2017 at 5:04 PM gary.ad...@oracle.com <gary.ad...@oracle.com>
wrote:

Try adding

     --disable-warnings-as-errors

to your configure command line.

A newer toolchain is sometimes stricter about the source code.
See "error:" in your build log mentions warnings being treated as errors.

On 6/17/17 3:53 AM, Pepper Lebeck-Jobe wrote:
I decided to try and figure out where the empty source path regression
was
coming from, and possibly fix it. See:
http://mail.openjdk.java.net/pipermail/jigsaw-dev/2017-June/012938.html

But, when I checked out the sources from mercurial and tried to build
them,
I ended up getting some errors. Anyone know whether I should be
suspecting
my development environment or the actual code?

Here's what I did based on these instructions.

http://hg.openjdk.java.net/jdk9/jdk9/file/023f93e511ba/common/doc/building.md
$>  hg clone http://hg.openjdk.java.net/jdk9/jdk9 openJDK
$> cd openJDK
$> bash ./get_source.sh
$> bash ./configure --with-boot-jdk=$JAVA_HOME
Output here:
https://drive.google.com/file/d/0Byp8Kl9b7wdibzk2TEFzN3ExVXc/view
$> make clean
$> make all LOG=debug
Output here:
https://drive.google.com/file/d/0Byp8Kl9b7wdiSEpVeHNjSDBIZTA/view

Any help is appreciated. I *think* I have installed the prerequisites
according to the instructions although my version of XCode (8.3.3) is
considerably newer. It wasn't clear of XCode 6.3 was a minimum
requirement
or an exact requirement.

Thanks,
Pepper



Reply via email to