Date: Wed, 4 Jun 2003 07:31:22 +0100 From: Antony T Curtis <antony.t.curtis@ntlworld.com> To: freebsd-java@FreeBSD.ORG Subject: Re: Fwd: Re: Native JDK with libthr/libkse Message-ID: <200306040731.23132.antony.t.curtis@ntlworld.com> In-Reply-To: <Pine.BSF.4.05.10306030744560.24448-100000@misery.sdf.com> References: <Pine.BSF.4.05.10306030744560.24448-100000@misery.sdf.com>
next in thread | previous in thread | raw e-mail | index | archive | help
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 03 June 2003 3:49 pm, Tom Samplonius wrote: > On Tue, 3 Jun 2003, Daniel Eischen wrote: > > ... > > > I was more interested in the statement that "jdk is only guaranteed > > to work with libc_r" that one of the Java developers posted. I > > took it to mean that the implementation of our jdk is geared > > towards libc_r (perhaps knowing internal stuff about how libc_r > > works). I don't want anything like that to stop us, and we > > can add some common APIs to the threads libraries if needed > > to support it. > > I don't think jdk uses any libc_r internals. I believe it is just that > jdk1.4.1 is a very large and very complex application, and the jdk > developers don't want to have to track libkse/libthr issues when jdk1.4.1 > is still beta and requires plenty more work. I know the Java developers > are trying to get jdk1.4.1 to the point it can pass Sun's TCK, so it can > be distributed as a binary. AFAIK, jdk1.3.1 still uses some libc_r internals unless the patch I sent to= =20 this list and Munehiro Matsuda did more work on is applied. =2D --=20 Antony T Curtis BSc Unix Analyst Programmer http://homepage.ntlworld.com/antony.t.curtis/ =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+3ZI7ql7dp2cddmIRAtwLAKDC+6BOuVmdNCD9TsxSldGEuJrz2QCgkDnA K0vmYwrAg1gOKbxIl1gzD14=3D =3DD143 =2D----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200306040731.23132.antony.t.curtis>