On Wed, Oct 29, 2003 at 03:28:32PM -0700, Scott Long wrote: > I just tried running the Diablo JDK under -current from yesterday (with > the libm fix from a few days ago). It does not look good; possibly an > issue with both the compat libc and native libc being linked in? Maybe > libm.so is still bringing in the native libc.so? We don't install the > 4.x libm into compat, and I don't have any 4.x machine around to steal it > from, so I can't test out that theory. The binary is linked to: /usr/lib/libm.so.2 /usr/lib/compat/libc.so.4 (and others) (recall: the source of the libm problems was that libc.so.5 was *not* linked in). I'm not sure why gdb says otherwise - perhaps it's confused about the library paths. Perhaps there's some kind of ABI problem here that java is choking on. Kris
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:27 UTC