On Sat, Mar 29, 2003 at 04:50:08PM -0600, Rich Smrcina wrote: > OK, it is a shell script! I found some discussion on this list some time back > about a java wrapper for the WAS installer and here it is. The discussion > also mentioned that the fix was to comment out the line: > > export LD_ASSUME_KERNEL=2.2.5
One possible workaround: add this one later on. Maybe in the call to java. e.g: maybe you need to replace somewhere in the script java with: LD_ASSUME_KERNEL=2.2.5 java Another option: locate the real java binary and replace it with a script that does something like: #!/bin/sh # set up environment LD_ASSUME_KERNEL=2.2.5 export LD_ASSUME_KERNEL # execute the original binary with all the command-line parameters: exec java_binary.real "$@" Although this maybe totally unrelated. > > If I do that I get this java exception: > > webst:/mnt/was # ./install.sh > Exception in thread "main" java.lang.UnsatisfiedLinkError: > /mnt/was/java/jre/bin/libawt.so: libXt.so.6: cannot open shared object file: > No such file or directory Is there a file called libXt.so.6 somewhere in the installation tree? > at java.lang.ClassLoader$NativeLibrary.load(Native Method) > at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1470) > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1346) > > Which looks to be complaining about not having access to a graphics > environment. I would normally export the display before executing this, so I > will try that tomorrow when I am on site at the customer. It's not that. This is not an error coming from Xlibs. This is an error from dynamic loader. -- Tzafrir Cohen +---------------------------+ http://www.technion.ac.il/~tzafrir/ |vim is a mutt's best friend| mailto:[EMAIL PROTECTED] +---------------------------+
