Self-built JDK has troubles reading jar-files

Hello,

I've just tried syncing with master, however my build doesn't seem to
be able to handle jar-files - even with a fresh clone of jdk7/jdk or
jdk//2d/jdk:

[ce@localhost linux-i586]$ bin/java -Dsun.java2d.xrender=True -jar
/fc8/usr/j.jar
Exception in thread "main" java.lang.NoClassDefFoundError: java2d/Java2Demo
        at java.lang.ClassLoader.findBootstrapClass(Native Method)
        at java.lang.ClassLoader.findBootstrapClassOrNull(ClassLoader.java:10
        at java.lang.ClassLoader.loadClass(ClassLoader.java:388)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:386)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:325)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:332)
        at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:1

Applications start up, after I unzip their jar-files and state the
main-class explicitly.

Any ideas what could be the problem? I am building on Fedora12 Beta, x86.

Thank you in advance, Clemens

[gnu_andrew]

2009/11/3 Clemens Eisserer <linuxhippy@...>:

> Hello,
>
> I've just tried syncing with master, however my build doesn't seem to
> be able to handle jar-files - even with a fresh clone of jdk7/jdk or
> jdk//2d/jdk:
>
> [ce@localhost linux-i586]$ bin/java -Dsun.java2d.xrender=True -jar
> /fc8/usr/j.jar
> Exception in thread "main" java.lang.NoClassDefFoundError: java2d/Java2Demo
>        at java.lang.ClassLoader.findBootstrapClass(Native Method)
>        at java.lang.ClassLoader.findBootstrapClassOrNull(ClassLoader.java:10
>        at java.lang.ClassLoader.loadClass(ClassLoader.java:388)
>        at java.lang.ClassLoader.loadClass(ClassLoader.java:386)
>        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:325)
>        at java.lang.ClassLoader.loadClass(ClassLoader.java:332)
>        at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:1
>
> Applications start up, after I unzip their jar-files and state the
> main-class explicitly.
>
> Any ideas what could be the problem? I am building on Fedora12 Beta, x86.
>
> Thank you in advance, Clemens
>

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.
--
Andrew :-)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8

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
>
> 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
           /home/ce/jdkbuild/jre/lib/i386/server/libjvm.so
       and/or check your value of ALT_HOTSPOT_SERV

Thanks, Clemens

[gnu_andrew]

2009/11/3 Clemens Eisserer <linuxhippy@...>:

> 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
>>
>> 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
>           /home/ce/jdkbuild/jre/lib/i386/server/libjvm.so
>       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

make

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. (http://www.redhat.com)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8

[Kelly O'Hair]

If it is complaining about libjsig.so,
then you need this changeset in the jdk7/jdk repository.

http://hg.openjdk.java.net/jdk7/jdk7/jdk/rev/8885b2256507

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
further.
Where did you get the forest from?
http://hg.openjdk.java.net/jdk7/jdk7  ???

-kto

Andrew John Hughes wrote:

> 2009/11/3 Clemens Eisserer <linuxhippy@...>:
>> 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
>>>
>>> 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
>>           /home/ce/jdkbuild/jre/lib/i386/server/libjvm.so
>>       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
>
> make
>
> You don't need binary plugs or any of these import statements, and
> they are probably confusing things.

[gnu_andrew]

2009/11/3 Kelly O'Hair <Kelly.Ohair@...>:

>
> If it is complaining about libjsig.so,
> then you need this changeset in the jdk7/jdk repository.
>
> http://hg.openjdk.java.net/jdk7/jdk7/jdk/rev/8885b2256507
>
> 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
> further.
> Where did you get the forest from?
> http://hg.openjdk.java.net/jdk7/jdk7  ???
>
> -kto
>

There's still the FontManager issue with b75, so for now I'd recommend m5:

http://hg.openjdk.java.net/jdk7/m5

which is currently b75 + build forest promotion + jsr166y

> Andrew John Hughes wrote:
>>
>> 2009/11/3 Clemens Eisserer <linuxhippy@...>:
>>>
>>> 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
>>>>
>>>> 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
>>>          /home/ce/jdkbuild/jre/lib/i386/server/libjvm.so
>>>      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
>>
>> make
>>
>> 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. (http://www.redhat.com)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8

[tim.bell]

Andrew John Hughes wrote:

> There's still the FontManager issue with b75, so for now I'd recommend m5:
>
> http://hg.openjdk.java.net/jdk7/m5
>
> which is currently b75 + build forest promotion + jsr166y

It should be, but my fault - the m5 forest does not have the build changests
yet, but it will in a few minutes.  I am pushing them now.

I merged m5 and build in a local forest for my test builds, but
forgot to update mg.  Sorry about the confusion.

Tim

[Kelly O'Hair]

I'm also doing a sync of the jdk7/jdk7 changes into jdk7/build.

But it won't happen until tomorrow.

-kto