Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA13730; Sat, 30 Dec 95 17:15:48 EST
Received: from liquor.cabi.net by MIT.EDU with SMTP
	id AA10807; Sat, 30 Dec 95 17:15:40 EST
Received: (from listadm@localhost) by liquor.cabi.net (8.6.12/8.6.12) id QAA12161; Sat, 30 Dec 1995 16:51:48 -0500
Resent-Date: Sat, 30 Dec 1995 16:51:48 -0500
Message-Id: <m0tW8RN-0003llC@bedlam.rahul.net>
Date: Sat, 30 Dec 95 13:03 PST
From: Bill Hogan <bhogan@rahul.net>
To: Alligator Descartes <descarte@hermetica.com>
Cc: bhogan@rahul.net, java-linux@java.blackdown.org
Subject: Re: getting started
In-Reply-To: <199512301859.SAA15796@fruitbat.mcqueen.com>
References: <m0tW6TU-0003llC@bedlam.rahul.net>
	<199512301859.SAA15796@fruitbat.mcqueen.com>
Reply-To: bhogan@rahul.net
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Resent-Message-Id: <"Xq_te.0.Zz2.oGRvm"@liquor>
Resent-From: java-linux@java.blackdown.org
X-Mailing-List: <java-linux@java.blackdown.org> archive/latest/809
X-Loop: java-linux@java.blackdown.org
Precedence: list
Resent-Sender: java-linux-request@java.blackdown.org

"AD" == Alligator Descartes <descarte@hermetica.com> writes:

  AD> I had exactly the same problem until I upgraded my libc and ld.so to the
  AD> following versions:
  >> 
  AD> libc-5.2.16
  AD> ld-so-1.7.12
  >> 
  AD> and the problem went away. Works fine after that...............
  >> 
  >> Hmm. 
  >> 
  >> Well, according to `ldd', both `javap' and `java' (i.e. `javac')
  >> reference
  >> 
  >> libc.so.5 => /G/java-linux/Debian.elf-libc/lib/libc.so.5.2.18.new
  >> 
  >> and, like I said, `javap' works fine, so I don't see how libc can be
  >> the problem.
  >> 
  >> So do you think ld.so-1.7.0 (vs. 1.7.12) might be the problem?

  AD> 1.7.10 didn't work. Flat. There's something in the HOWTO along those
  AD> lines. I'd recommend upgrading to 1.7.12.

     Ok, that did it.

     (I happen to be running a Debian-0.93 (a.out) setup, but it turns
out ld.so-1.7.14 has found its way into the elf-debian tree, so I
grabbed that instead.)

     The point of this exercise was to try to find the smallest set of
*additions to* my stock Debian-0.93 setup that would enable me to run
java-linux.

     To do this, I created an off-line directory

	/G/java-linux

into which I successively unpacked the following packages:


	1. Blackdown/Chapman java-linux `common' and `static' archives

		linux.jdk.common.tar.gz
		linux.jdk.x86-static-motif-bin.tar.gz

	2. Debian.elf-libc

		libc5-5.2.18-1.deb

	3. Debian.elf-x11r6lib

		elf-x11r6lib-3.1.2-1.deb

(and because Debian.elf-xpm was not yet available)

	4. the Slackware-3.0 x11 `xpm.tgz' package

	

   I then added the following three lines to my `/etc/ld.so.conf':

	/G/java-linux/Debian.elf-libc/lib
	/G/java-linux/Debian.elf-x11r6lib/lib
	/G/java-linux/Slackware-3.0-x11-xpm/usr/X11R6/lib

and upgraded to ld.so-1.7.14 as noted earlier.


     One more detail: Debian does not support `which', so I replaced
the call to `which' that occurs in `.java_wrapper' by `type -p':

/G/java-linux/java/bin # diff .java_wrapper original-.java_wrapper
------------------------------ quote ------------------------------
20,22c20
< echo ".java_wrapper sees PATH=$PATH"
< PRG=`type -p $0`
< echo "PRG=$PRG"
---
> PRG=`which $0` >/dev/null 2>&1
----------------------------- unquote ----------------------------


   A pointer from /usr/local/java to /G/java-linux/java is
required.


   And as soon as Xpm finds its way into the elf-debian tree, I will
grab it.

    Looking good!

    Bill
     

     

