java binary incompatibility on 5.x (Re: __fpclassifyd problem)
kris at obsecurity.org
Wed Oct 29 22:27:12 PST 2003
On Wed, Oct 29, 2003 at 10:40:29PM -0700, Greg Lewis wrote:
> On Wed, Oct 29, 2003 at 06:07:11PM -0800, Kris Kennaway wrote:
> > 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?
> I think its already fixed in CVS. I'll try and test it tomorrow. Does
> anyone know if ref5 has been updated to after the libm fix? I don't have
> a -CURRENT box at home to test on.
You should be able to roll your own libm and use LD_LIBRARY_PATH.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-java/attachments/20031029/ef46080d/attachment.bin
More information about the freebsd-java