Re: required Libraries

1999-10-08 Thread Jeff Galyan
Okay, here's how I understand the Blackdown builds of the VM: there is a fully dynamic version and a static version. To switch between them, you set an environment variable (I think). If you want to use the dynamically-linked VM, you have to have both X and Motif shared libraries on your system.

Re: required Libraries

1999-10-06 Thread Paolo Ciccone
On Wed, Oct 06, 1999 at 11:18:13AM -0400, Jacob Nikom wrote: > Hi, > > I am interested in this discussion, but I am trying to convert it > into more plain English. I always thought that the lightweight > components are peerless. Swing still needs some heaviweight componentes, namely the AWT F

Re: required Libraries

1999-10-06 Thread Nathan Meyers
Jacob Nikom wrote: > > Hi, > > I am interested in this discussion, but I am trying to convert it into > more > plain English. I always thought that the lightweight components are > peerless. > They don't need X libraries and work "directly" with OS and hardware. Lightweight or heavyweight, you

Re: required Libraries

1999-10-06 Thread Jacob Nikom
Hi, I am interested in this discussion, but I am trying to convert it into more plain English. I always thought that the lightweight components are peerless. They don't need X libraries and work "directly" with OS and hardware. Swing was claimed as lightweight component based package, so it s

Re: required Libraries

1999-10-05 Thread Nathan Meyers
Jeff Galyan wrote: > > Java *always* requires Motif and X libraries. Even on Solaris. End of > story. "Requires" meaning that Blackdown requires an *external* libXm? Not necessarily. JDK1.2pre2 certainly doesn't (libXm appears to be statically linked into libawt.so), and I believe something simi

Re: required Libraries

1999-10-05 Thread Chris Abbey
At 20:52 10/5/99 -0600, Jeff Galyan wrote: >Java *always* requires Motif and X libraries. Even on Solaris. End of >story. And thus the blackdown port is more advanced than the Solaris release. I'd highly recommend that you investigate the "not-static" binaries, these have no X widgets linked in

Re: required Libraries

1999-10-05 Thread Jeff Galyan
Java *always* requires Motif and X libraries. Even on Solaris. End of story. --Jeff Carsten Hoeger wrote: > > On Sat, Oct 02, Jeff Galyan wrote: > > > Actually, libXm.so is Motif, which is required by AWT, and therefore > > Java. You'll need to get a Motif distribution (I use RedHat Motif 2.1

Re: required Libraries

1999-10-03 Thread Carsten Hoeger
On Sat, Oct 02, Jeff Galyan wrote: > Actually, libXm.so is Motif, which is required by AWT, and therefore > Java. You'll need to get a Motif distribution (I use RedHat Motif 2.1.10 > with no problems). That's not true! There are both, static and dynamic linked versions of the java vm. The depen

Re: required Libraries

1999-10-02 Thread Jeff Galyan
Actually, libXm.so is Motif, which is required by AWT, and therefore Java. You'll need to get a Motif distribution (I use RedHat Motif 2.1.10 with no problems). --Jeff Carsten Hoeger wrote: > > On Tue, Sep 28, Rolf wrote: > > > I am running a SuSe Linux 6.1 on my box and have libc 2 installe

RE: required Libraries

1999-09-28 Thread Burkhart,Kelly
Isn't libXm the motif lib? Try using the static motif JDK or installing motif. Does the JDK work with lesstif? > -Original Message- > From: Rolf [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, September 28, 1999 5:26 AM > To: [EMAIL PROTECTED] > Subject: required Libraries > > > Hi, > >

Re: required Libraries

1999-09-28 Thread Carsten Hoeger
On Tue, Sep 28, Rolf wrote: > I am running a SuSe Linux 6.1 on my box and have libc 2 installed on my > system. > When I try to install JDK 1.1.1 using rpm, I get the message libXm.so.2 > is needed by jdk1.1-1.1.7v1a-3. Where do I get this library ? Try 'rpm --nodeps --force yourrpmname.rpm'...