If you don't have linux, forget about this email.
As last year was a transition year on libc to glibc, many distributions of
linux didn't get it right. I had to update glibc with a rpm from my vendor
(Caldera Open Linux). Search your distribution's support site to find out if
glibc has been updated.
In addition, if you have updated your glibc, you may have to run ldconfig
(see page 199 of Running Linux, O'Rielly) for all of the links to update. I
have had no problems with jdk1.2.2 from Sun on Caldera Open Linux 2.3
(2.2.10 kernel version) with glibc 2.1.1 or 2.1.2. However, IBM Java2-13
required glibc 2.1.2 because of a glitch in Caldera's compilation of glibc.
Regards,
Lawrence
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jacek Laskowski
Sent: Friday, September 01, 2000 5:32 AM
To: Orion-Interest
Subject: Re: Which JDK to use?
"J.T. Wenting" wrote:
>
> I'm having trouble with glibc and java (Sun for now). I have glibc 2.1.3,
> JDK 1.2.2. When I try to start a Swing/AWT application I get a 'shared
> library not found' error.
> Anyone know something about that? non-GUI programs run fine.
I'm not sure about that, but I think I've seen something similar in the
past. The solution was to set LD_LIBRARY_PATH pointing out to
$JAVA_HOME/lib or so and all started to be working fine. I can't check
it out as I'm on Solaris, but I'm pretty sure it should help.
>
> Jeroen T. Wenting
> [EMAIL PROTECTED]
Jacek Laskowski
