@Martijn - as Magnus suggests, I would do the same, zap all the forests then clone and run get_source.sh.
I have had similar instances in the past and the above helped although the cause of the problem may sometimes elude us. Cheers, Mani On Fri, Feb 6, 2015 at 11:16 PM, Magnus Ihse Bursie < magnus.ihse.bur...@oracle.com> wrote: > On 2015-02-06 17:46, Martijn Verburg wrote: > >> >> /Users/karianna/Documents/workspace/AdoptOpenJDK_ >> projects/jdk9/build/macosx-x86_64-normal-server-release/ >> buildtools/interim_langtools.jar >> does not exist! So it's not being built correctly or moved to the right >> place. >> >> I'm not seeing any other clues (even at trace) that indicates why >> interim_langtools.jar has not been built.... >> > > Sometimes mercurial forests can get messed up. If an unmodified source > fails to compile after dist-clean, this can be the case. One thing to to is > to try and re-clone the forest. Make sure get_source.sh runs to completion > without any errors. > > Otherwise, you have narrowed down the issue quite well. We need to figure > out why interim_langtools.jar is not being built. > > Start by rm -rf build && configure. > > Then run "make interim-langtools". Check the contents of > build/$BUILD/buildtools. Is it there? If so, you should be able to do just > "make" and continue. > > Otherwise, start again with more logging. rm -rf build && configure && > make interim-langtools LOG=debug (trace is not being helpful). > > /Magnus > -- @theNeomatrix369 <http://twitter.com/theNeomatrix369>* | **Blog <http://neomatrix369.wordpress.com>** | *LJC Associate & LJC Advocate (@adoptopenjdk & @adoptajsr programs) *Meet-a-Project - *MutabilityDetector <https://github.com/MutabilityDetector>* | **Bitbucket <https://bitbucket.org/neomatrix369>* * | **Github <https://github.com/neomatrix369>* * | **LinkedIn <http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b>* *Come to Devoxx UK 2015:* http://www.devoxx.co.uk/ *Don't chase success, rather aim for "Excellence", and success will come chasing after you!*
