java binary incompatibility on 5.x (Re: __fpclassifyd problem)

[Kris Kennaway]

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.

With help from peter and dwhite, we tracked down the cause to the following:

./jdk131.patches:+    dlMain = dlopen("/usr/lib/libc.so", RTLD_LAZY);
./jdk131.patches:+        void *dlMain = dlopen("/usr/lib/libc.so", RTLD_LAZY);

Java people, this is the cause of the binary incompatibility of 4.x
java binaries on 5.x.  Can someone please fix?

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20031029/c330202d/attachment.bin