While building images in a mercurial workspace updated as of today, I get
/home/martinrb/ws/build/build/linux-i586/classes/com/sun/tools/classfile
: no such file or directory
/home/martinrb/ws/build/build/linux-i586/classes/com/sun/tools/javap :
no such file or directory
make[1]: *** [initial-image-jdk] Error 1
make[1]: Leaving directory `/usr/local/google/home/martin/ws/build/jdk/make'
make: *** [jdk-build] Error 2
The failing command appears to be a (very long) jar command
invoked from Release.gmk
$(BOOT_JAR_CMD) c0f $(LIBDIR)/tools.jar $(addprefix \
-C $(CLASSBINDIR) , $(TOOLS)) \
$(JAR_JFLAGS)
This happens both building a complete OpenJDK forest and
when building the "jdk" repository.
32-bit linux Ubuntu 6.06
This is a very recently introduced failure (over the past week?).
Fortunately, there is a workaround that's not too painful.
Simply create the two missing directories and restart the build.
Even javap works!
I'm currently successfully building like this:
make clobber; mkdir -p
../build/linux-i586/classes/com/sun/tools/{classfile,javap}; make all
images
But it's still a P1 bug, right?
Martin
