Self-built JDK has troubles reading jar-files

Andrew John Hughes gnu_andrew at
Tue Nov 3 22:33:51 UTC 2009

2009/11/3 Clemens Eisserer <linuxhippy at>:
> 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
>           /home/ce/jdkbuild/jre/lib/i386/server/
>       and/or check your value of ALT_HOTSPOT_SERV
> Thanks, Clemens

You can cut that down to:

export ALT_BOOTDIR=/home/ce/Programme/jdk7b75/
export PATH=$PATH:/home/ce/Development/tools/apache-ant-1.6.5/bin/
export ALT_OUTPUTDIR=/home/ce/jdk2d_try/jdk/build/linux-i586


You don't need binary plugs or any of these import statements, and
they are probably confusing things.
Andrew :-)

Free Java Software Engineer
Red Hat, Inc. (

Support Free Java!
Contribute to GNU Classpath and the OpenJDK

PGP Key: 94EFD9D8 (
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8

More information about the build-dev mailing list