Date: Wed, 29 Oct 2003 21:06:09 -0700 From: Scott Long <scottl@freebsd.org> To: Kris Kennaway <kris@obsecurity.org> Cc: John Angelmo <john@adminforum.se> Subject: Re: java binary incompatibility on 5.x (Re: __fpclassifyd problem) Message-ID: <3FA08E31.9030701@freebsd.org> In-Reply-To: <20031030020711.GA24468@rot13.obsecurity.org> References: <3F92E129.10307@veidit.net> <20031028034630.GC32916@VARK.homeunix.com> <20031028090337.E27950@carver.gumbysoft.com> <3FA01F71.1020203@adminforum.se> <20031029211951.GA12398@rot13.obsecurity.org> <20031029152202.C7702@pooker.samsco.home> <20031030020711.GA24468@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
>
> Kris
Thanks for tracking this down.
Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FA08E31.9030701>