OpenJDK 7 build failure in com/sun/tools
Tim.Bell at Sun.COM
Wed Jul 2 16:55:26 PDT 2008
> While building images in a mercurial workspace updated as of today, I get
> : no such file or directory
> /home/martinrb/ws/build/build/linux-i586/classes/com/sun/tools/javap :
> no such file or directory
> make: *** [initial-image-jdk] Error 1
> make: Leaving directory `/usr/local/google/home/martin/ws/build/jdk/make'
> make: *** [jdk-build] Error 2
> This happens both building a complete OpenJDK forest and
> when building the "jdk" repository.
I will test the "complete OpenJDK forest" part. See below for the "when building the "jdk"
When you build only jdk the other pieces are assembled from the latest promoted JDK (or your
ALT_BUILD_JDK_IMPORT_PATH). The new classes Jon added for 6708729/6439940 are not there yet,
so they are not pulled over. The build fails later when trying to assemble tools.jar. This is
an outcome of code and Makefile changes that span two repositories.
Until b30 is promoted, or your ALT_BUILD_JDK_IMPORT_PATH is updated by some other means to a
build that includes the 6708729/6439940 fixes, you _must_ do a control build of (at least)
langtools plus jdk to get the new classes added. See email thread  from last month for a
discussion of this.
Your control build may include any or all of the rest (corba hotspot jaxp jaxws etc...) if you
> This is a very recently introduced failure (over the past week?).
The changes went into jdk7/jdk7 (the master) when I pushed the jdk7/tl b30 changes on 25 June.
> Fortunately, there is a workaround that's not too painful.
> Simply create the two missing directories and restart the build.
> Even javap works!
I think if you check you will find that you got the 'old' javap from BOOTDIR (nothing wrong
with that - it still works as ever) but the new classes added by 6708729/6439940 are not present.
More information about the compiler-dev