> Aaron Gaudio writes:
Aaron> I wouldn't recommend glibc 2.0.110 (or 111 for that
Aaron> matter). Java isn't the only thing it breaks (try compiling a
Aaron> C++ program that uses iostreams). It's not ready for prime time
Aaron> just yet.
You did read the glibc FAQ that comes with glibc2.0.1
I wouldn't recommend glibc 2.0.110 (or 111 for that matter). Java isn't the
only thing it breaks (try compiling a C++ program that uses iostreams). It's
not ready for prime time just yet.
And so the chronicles report that SHUDO Kazuyuki spake thusly unto the masses:
>
> Hi,
>
> I've updated gli
> SHUDO Kazuyuki writes:
> Hi,
> I've updated glibc from 2.0.7 to 2.0.110.
> Then JDK 1.1.7v1a can't work at all.
> Java command says,
> % java
> /usr/local/java/bin/i586/green_threads/java: error in loading shared libraries:
>/usr/local/java/lib/i586/green_threads/libjava.so: un
Hi,
I've updated glibc from 2.0.7 to 2.0.110.
Then JDK 1.1.7v1a can't work at all.
Java command says,
% java
/usr/local/java/bin/i586/green_threads/java: error in loading shared libraries:
/usr/local/java/lib/i586/green_threads/libjava.so: undefined symbol: _dl_symbol_value
Glibc 2.0.7 hav
