Date: Thu, 28 Nov 96 22:47:52 From: "Jake Hamby" <jehamby@lightside.com> To: Mark Mayo <mark@quickweb.com> Cc: Jeffrey Hsu <hsu@freefall.freebsd.org>, current@freefall.freebsd.org Subject: Re: new JDK release Message-ID: <199611290648.WAA05790@covina.lightside.com>
next in thread | raw e-mail | index | archive | help
Mark Mayo wrote: >On Tue, 26 Nov 1996, Jeffrey Hsu wrote: >2) I now get annoying X messages (even when compiling !?) : >(null): warning: /usr/X11R6/lib/libXext.so.6.0: minor version 0 older than >expected 1, using it anyway >(null): warning: /usr/X11R6/lib/libX11.so.6.0: minor version 0 older than >expected 1, using it anyway > >Is this normal, and why is the compiler giving me these errors? I get the >warning from serveral other programs too - I'm mostly just curious about >javac's need for X stuff :-) The JDK was compiled with the X11R6.1 libraries. You can upgrade to the newest XFree86 (3.2), which has these libraries, or stay with the older XFree86 and ignore the warnings. The libraries should be forwards and backwards compatible (that's why the minor version number was bumped and not the major one), but the run-time loader issues a warning to alert you that the program was compiled (and therefore tested) with a later version of the library than what you're using. >One other thing, does anyone else notice that it takes _forever_ for the >java interpreter to bring up a Dialog class?? My machine takes about 5 >seconds to pop up a dialog (with just a label on it). This seems wrong >since my machine is a PPro, and also I noticed that almost no CPU is being >used - it just seems to stall for a while (the calling Frame is still >functional though). I've noticed this too! I think it's a Motif thing, but it is annoying. I can tell you that upgrading to the newer XFree86 (as I mentioned above) won't change anything. Fortunately, after the first AWT pops up, the graphics speed is the same as Linux, Windows, or Solaris. For a while when I was using the Castanet Tuner (on my 486), it seemed *much* slower than under Windows, but then I remembered I had stuffed the Symantec JIT compiler into the Windows version (JAVA.DLL) and forgot about it... :-) >P.S. Are there any plans on supporting 65K colors in the interpreter? My >AWT apps run without crashing, but they are shades of blue only while in >65K hi-color mode =) I think *all* of the UNIX JDK's support 64k-colors poorly. You can hardly blame Jeffrey for that, eh? :-) -- Jake
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611290648.WAA05790>