Self-built JDK has troubles reading jar-files

Clemens Eisserer linuxhippy at
Tue Nov 3 22:31:29 UTC 2009

Hi Andrew,

> Difficult to say from just that.  Have you tried using the freshly
> built JDK to build itself?  It's a quick acid test of a new build, and
> something IcedTea does by default.

I know thats no excuse, but I haven't played a lot with building OpenJDK.
I was happy when I found a way to build it reliable, I usually do that
with the following script:

> #!/bin/sh
> export ALT_BOOTDIR=/home/ce/Programme/jdk7b75/
> export ALT_HOTSPOT_IMPORT_PATH=/home/ce/Programme/jdk7b75
> export ALT_BINARY_PLUGS_PATH=/fc8/home/ce/OpenJDK7/openjdk-binary-plugs
> export PATH=$PATH:/home/ce/Development/tools/apache-ant-1.6.5/bin/
> export ALT_OUTPUTDIR=/home/ce/jdk2d_try/jdk/build/linux-i586
> export ALT_JDK_IMPORT_PATH=/home/ce/Programme/jdk7b75
> export ALT_JIBX_LIBS_PATH=/home/ce/Development/tools/jibx/lib

When I try to use the self-built jdk, it fails, because the files in
linux-i586 don't have the structure the makefile searches for, and it
fails with:
ERROR: HOTSPOT_SERVER_PATH does not point to a valid HotSpot VM.
       Please check your access to
       and/or check your value of ALT_HOTSPOT_SERV

Thanks, Clemens

More information about the build-dev mailing list