Steve Byrne writes:
> > Great, is this the version for glibc ?
> Nope -- libc5 -- that's what I build with. If you've got a fast network
> connection, it's still worth a download -- I think that if you've got a recent
> enough version of glibc (and libdl 2.x) that you still may be able to use
> this version successfully.
Steve,
I just installed RH 5.1, latest glibc (2.0.7.-13, libdl-2.0.7.so).
I also got me the Errata (X), libc-5_4_45, gcc-2.8.1.... ad
nauseam. I also downloaded 1.1.6v2 (on a slow connection, took 4h).
Result:
gcc -L/opt/local/java/jdk/lib/i586/green_threads/ -ljava invoke.o -o invoke
/usr/i486-linux-libc5/lib/libm.so.5: undefined reference to `__getfpucw'
That is libm.so.5.0.9 plus libc.so.5.4.45. It is the same with
using libm.so.5.0.6 plus libc.so.5.3.12. What combination do you
suggest? JDK does not work w/o a libc5 libm, but seems to lack
one matching it's own local libc5.
b.
P.S.: I used jdk1.1.5v5-980311 to at least link. Here, the core dump
I get with my C app that only *links* "-ljava -ldl" (it does not
even include jni.h) allegedly traces back to (using -ljava_g):
../../../../src/genunix/java/green_threads/src/iomgr.c:1597.
This is gcc-2.7.2.3, and egcs-2.90.27 980315 (egcs-1.0.2 release).
A core also occurs with jdk-1_1_5-1_3-glibc-dynamic_tar.gz.
