Date: Wed, 29 Oct 2003 18:07:11 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Scott Long <scottl@freebsd.org> Cc: Kris Kennaway <kris@obsecurity.org> Subject: java binary incompatibility on 5.x (Re: __fpclassifyd problem) Message-ID: <20031030020711.GA24468@rot13.obsecurity.org> In-Reply-To: <20031029152202.C7702@pooker.samsco.home> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
--X1bOJ3K7DJ5YkBrT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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
--X1bOJ3K7DJ5YkBrT
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQE/oHJPWry0BWjoQKURAv0YAKDaZaC5iEqd36i/TCD+lWo/tYz0QACgz4Gi
6+7dko/fmzHHPSDLTlOvdcc=
=ra6w
-----END PGP SIGNATURE-----
--X1bOJ3K7DJ5YkBrT--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031030020711.GA24468>