Thatis great and all.....but where can we send the pizza to thank you for
all the hard work that you have put into making any of these versions as
amazing as they are!. And of course saving us from NT and the like.
Pooh Bear -- "I am just a bear of little brain"
On Mon, 14 Sep 1998, Kevin B. Hendricks wrote:
> JDK 116 v4a Issue Resolutions: Please READ!
> --------------------------------------------
>
> There have been a large number of reported problems with JDSK 116 v4a that
> are caused by incompatible system shared libraries in one way or another.
> Problems like these are really why a Linux distribution standard is
> desperately needed (IMHO).
>
> In an attempt to prevent the Jitterbug Database from overflowing with
> problems that are distribution dependent and easily fixed, here are some
> things to Please try before submitting a bug report:
>
>
> PROBLEM: SegFaults
> FIX:
> The system shared libraries that are shipped with the JDK are in some way
> incompatible with the shared libraries in your distribution. To fix this
> problem simply remove the system shared libraries that came with the JDK so
> that the system shared libraries of your own system are used.
> - remove libc and libdl from $JAVA_HOME/lib/XXX/green_threads/
> where XXX is your archictecture
>
>
>
> PROBLEM: font problems with messages like:
> Warning:
> Name: textfield
> Class: XmTextField
> Character 'x' not supported in font. Discarded.
> FIX:
> There seems to be a problem with Motif loading and finding the
> libraries that deal with Locale issues on some distributions. To
> work around this issue make sure libBrokenLocale.so is found and
> linked to first (a Motif issue?) by doing the following:
>
> LD_PRELOAD=/usr/lib/libBrokenLocale.so java _name_of_class_file
>
> If this fixes your problem, you can edit your $JAVA_HOME/bin/.java_wrapper
> so that this is done automatically.
>
>
>
> PROBLEM: SO_LINGER, MULTICAST Socket error, bad parameter
> FIX:
> This was my fault. I was trying to improve socket performance and
> accidentally left some code in that I should have reverted.
> The problem is known and a fix will appear in the next release. If you
> roll your own from source, please contact me directly and I will post
> a patch for you. If you don't, and this is a "show stopper!" for you,
> I am sure we can make a development release available to hold you until
> the next release, or you can revert back to v2 or v3.
>
>
>
> We are working on coming up with a better solution to all of these problems.
> If we don't include system shared libraries in the JDK, then we get
> hundreds of reports of SEGFAULTS on startup from people whose systems are
> not up to date. If we do include them, we run the risk of having system
> incompatibilities like the ones we are seeing now. Our previous solution
> was to ship the key system shared librtaries with the JDK, knowing that
> people could easily remove them if incompatitibilities arose. We are now
> working on an install script that will automatically check these libraries
> and then "do the right thing".
>
> Also, Metro Link has nicely donated updated copies of its RedHat Motif to
> be used by the porting team for releases. This will hopefully clear up the
> font / textfield related problems in the future.
>
>
> I hope this information helps.
>
> Thanks for your support and sorry for any inconvenience.
>
> Kevin B. Hendricks
> Blackdown Java Porting Team
> [EMAIL PROTECTED]
>
>
>
>
>
>
>
> --------------------------------------------------------------------------
> Kevin B. Hendricks
> Associate Professor of Operations and Information Technology
> School of Business, College of William & Mary, 307 Tyler Hall,
> P.O.Box 8795, Williamsburg, VA 23187-8795
> (757) 221-1702, [EMAIL PROTECTED]; http://business.tyler.wm.edu
>
>
