Self-built JDK has troubles reading jar-files
Kelly.Ohair at Sun.COM
Tue Nov 3 22:54:03 UTC 2009
If it is complaining about libjsig.so,
then you need this changeset in the jdk7/jdk repository.
The Makefile jdk7/jdk/make/java/redist/Makefile is the jdk
Makefile that copies the hotspot build into a jdk image.
There was some recent changes in hotspot that required a
change in this jdk makefile.
A fresh master forest should build ok, if it doesn't I need to look
Where did you get the forest from?
Andrew John Hughes wrote:
> 2009/11/3 Clemens Eisserer <linuxhippy at gmail.com>:
>> 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:
>>> 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
>>> make ARCH_DATA_MODEL=32 FASTDEBUG=false DEV_ONLY=false
>> 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
> 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.
More information about the build-dev