From owner-freebsd-current@FreeBSD.ORG Fri Oct 24 09:51:53 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 2567416A4BF; Fri, 24 Oct 2003 09:51:53 -0700 (PDT) Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F0F443FE0; Fri, 24 Oct 2003 09:51:51 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from emerger.yogotech.com (emerger.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3p2a/8.9.3) with ESMTP id KAA09214; Fri, 24 Oct 2003 10:51:45 -0600 (MDT) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by emerger.yogotech.com (8.12.9/8.12.8) id h9OGpZFO097907; Fri, 24 Oct 2003 10:51:35 -0600 (MDT) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16281.22674.121623.574110@emerger.yogotech.com> Date: Fri, 24 Oct 2003 10:51:30 -0600 To: Scott Long In-Reply-To: <3F975B45.6010504@freebsd.org> References: <20031023041544.068CD2A7EA@canning.wemm.org> <3F975B45.6010504@freebsd.org> X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid cc: deischen@freebsd.org cc: re@freebsd.org cc: current@freebsd.org cc: kris@obsecurity.org cc: "M. Warner Losh" Subject: Re: __fpclassifyd problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Nate Williams List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Oct 2003 16:51:53 -0000 [ add compatability hacks to libm ] > > We tried this at usenix, but it still didn't work. Obviously there is more > > going on. > > > > Before anybody goes and bumps libraries etc, it would be useful to know if > > running a statically linked jvm will work on -current. > > This sounds like a good plan, though it should be noted that statically > linking the jvm executable will reder it useless since it won't be able > to dl_open any of the essential JNI modules. Not just the JNI modules, but basically *all* the modules are dl_opened, so a staticially linked modern JVM can't realistically be created. The last time we were able to create a static JVM was JDK1.1. I spent many weeks attempting to create one for 1.2, and finally gave up. Nate