A FULL jdk control build involves having the following directories:
control langtools corba jaxp jaxws hotspot j2se
And you are right, you should not need to set ALT_JDK_IMPORT_PATH when doing
a full control build.
The ALT_JDK_IMPORT_PATH should just be used when the build detects one
of the above areas is not participating in the build.
Doing a 'cd control/make && gnumake' should first build langtools with the
BOOT jdk (ALT_BOOTDIR), then build hotspot, corba, jaxp, jaxws, and finally
go into j2se to build everything else and construct the j2sdk-image.
Do you have all these areas? It seems like the Makefiles think you do not.
-kto
Nicholas Riley wrote:
On Oct 30, 2007, at 5:47 PM, Kelly O'Hair wrote:
The directory in ALT_JDK_IMPORT_PATH
(in your case /mounts/hel/disks/0/shared-data/njriley/openjdk/old)
should contain a jdk image, e.g. bin, lib, include, jre/bin, jre/lib,
lib/tools.jar,
jre/lib/rt.jar. etc...
Does it?
No, it only contained some of that. Looks like I needed to point it to
the j2sdk-image subdirectory of the directory I used. This got further:
/mounts/hel/disks/0/shared-data/njriley/openjdk/jdk/control/build/linux-i586/classes/META-INF/services/com.sun.tools.xjc.Plugin
: no such file or directory
make[1]: *** [initial-image-jdk] Error 1
make[1]: Leaving directory
`/mounts/hel/disks/0/shared-data/njriley/openjdk/jdk/j2se/make'
make: *** [j2se-build] Error 2
I'm still confused as to why setting ALT_JDK_IMPORT_PATH was necessary
at all. It wasn't necessary before; all I want to do is do a full build.
