Re: libc upgrade has broken jdk 1.3?

[Brett Sealey <bretts@mortbay.com>]

About 6 weeks ago people started reporting this problem.

I think only jdk-1.4.1 is OK with the new libc6

Apparently the old JVMs used a non-public api which the libc people 
don't/won't support.

I'm thinking I will probably need to keep the old libraries handy for the 
older JVMs once I upgrade. It is a damn pity though.


On Mon, 2 Dec 2002, Greg Wilkins wrote:

> 
> I get the same thing with 1.3.1_06
> 
> Greg Wilkins wrote:>
> > I've been using Suns jdk1.3.1_02 on debian sid.
> > 
> > I just updated my libc to libc-2.3.1.so and now when I run java I get:
> > 
> >   Error occurred during initialization of VM
> >   Unable to load native library: 
> > /usr/local/java/jdk/jdk1.3.1_02/jre/lib/i386/libjava.so: symbol 
> > __libc_wait, version GLIBC_2.0  not defined in file libc.so.6 with link 
> > time reference
> > 
> > 
> > An ldd of the java libs looks OK.
> > 
> > ldd /usr/local/java/jdk/jdk1.3.1_02/jre/lib/i386/libjava.so
> >         libjvm.so => 
> > /usr/local/java/jdk/jdk1.3.1_02/jre/lib/i386/classic/libjvm.so (0x40024000)
> >         libverify.so => 
> > /usr/local/java/jdk/jdk1.3.1_02/jre/lib/i386/libverify.so (0x400b8000)
> >         libnsl.so.1 => /lib/libnsl.so.1 (0x400d8000)
> >         libdl.so.2 => /lib/libdl.so.2 (0x400eb000)
> >         libc.so.6 => /lib/libc.so.6 (0x400ee000)
> >         libm.so.6 => /lib/libm.so.6 (0x40201000)
> >         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
> > 
> > 
> > What can I do to fix this (other than role back my libc)?
> > 
> > 
> 
> 
> 
>