From owner-freebsd-current@FreeBSD.ORG Wed Oct 29 18:07:13 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C0C116A4CE; Wed, 29 Oct 2003 18:07:13 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-234.dsl.lsan03.pacbell.net [63.207.60.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50BDC43FDF; Wed, 29 Oct 2003 18:07:12 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 02C5F66D74; Wed, 29 Oct 2003 18:07:12 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id CA456840; Wed, 29 Oct 2003 18:07:11 -0800 (PST) Date: Wed, 29 Oct 2003 18:07:11 -0800 From: Kris Kennaway To: Scott Long Message-ID: <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> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT" Content-Disposition: inline In-Reply-To: <20031029152202.C7702@pooker.samsco.home> User-Agent: Mutt/1.4.1i cc: java@FreeBSD.org cc: David Schultz cc: John Angelmo cc: current@freebsd.org cc: Kris Kennaway Subject: java binary incompatibility on 5.x (Re: __fpclassifyd problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2003 02:07:13 -0000 --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--