From owner-freebsd-java@FreeBSD.ORG Wed Jan 26 02:44:41 2005 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 719A816A4CE for ; Wed, 26 Jan 2005 02:44:41 +0000 (GMT) Received: from wildbean.clapper.org (wildbean.clapper.org [216.158.26.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B00D643D49 for ; Wed, 26 Jan 2005 02:44:40 +0000 (GMT) (envelope-from bmc@clapper.org) Received: from condor.inside.clapper.org (phantom@condor.inside.clapper.org [172.16.87.5]) by wildbean.clapper.org (8.13.1/8.13.1) with ESMTP id j0Q2idCl018325; Tue, 25 Jan 2005 21:44:40 -0500 (EST) Received: from z.inside.clapper.org (z.inside.clapper.org [172.16.87.2]) j0Q2idk9040950; Tue, 25 Jan 2005 21:44:39 -0500 (EST) Message-Id: <200501260244.j0Q2idk9040950@condor.inside.clapper.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 25 Jan 2005 21:44:40 -0500 To: Matt Meola From: Brian Clapper In-Reply-To: <1106678783.55474.12.camel@matt.den-esniff.com> References: <1106678783.55474.12.camel@matt.den-esniff.com> X-Mailer: VM 7.17 under Emacs 21.3.1 X-Face: /perrud9r1.|7j.*=/6)a%vZ$^sBn!P[?+}vWBxd1ps{4hd2ZOw8]u&t';}(kj=x; JpdSF7 1b<*T{.38]wnWl]j/ULRB*49qdsET_/)-siUd7A_n- List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 02:44:41 -0000 On 25 January, 2005, at 11:46 (-0700) Matt Meola wrote: > I can't get java to run unless I use the absolute path to the > executable. I looked through the archives, and saw someone else had > this problem back in June of last year, but I didn't see a resolution to > the issue... > > ldconfig -r tells me that /usr/local/jdk1.5.0/jre/lib/i386 is searched, > and the shared lib is in that directory. > > JAVA_HOME is set to /usr/local/jdk1.5.0. > Any ideas? > > # java -version > Error: could not find libjava.so > Error: could not find Java 2 Runtime Environment. > > # $JAVA_HOME/bin/java -version > java version "1.5.0-p1" > Java(TM) 2 Runtime Environment, Standard Edition (build > 1.5.0-p1-toor_25_jan_2005_09_13) > Java HotSpot(TM) Client VM (build 1.5.0-p1-toor_25_jan_2005_09_13, mixed > mode) I'm seeing the same behavior. I saw it with the port as well as the patch-and-build-yourself precursor to the port. My situation is the same as noted above. I'm running on 4.10-RELEASE. FWIW, I have had no trouble at all with the 1.4.2 native JDK; I've been using it for months. Brian Clapper, http://www.clapper.org/bmc/