i was just trying to see some of the probs in doing a "Native" port of the java 116
jdk.
Its one thing to try to get ur task ( java ) done, without having to go to other
software
packages to get it to go also ( like gdb, libdl.so, lesstiff ( a while back ), ld ) .
Since it seems possible ( as it is/has been DONE by some other group ) to do, i though
i'd give it a shot ( again ).
I'm not sure if the blackdown porters are into this NATIVE thread port - they are a
little secretive on what they are currently doing. Maybe an open collaboration?
Anyway, if i get that far, my bigger problem would be to find a dual cpu alpha to try
it
on, which would be the only way i know how to test the threading of the port. BUT that
is
a while away from now.
gat
Danny Backx wrote:
> Even if we're aiming for 1.2, it should be possible to
> make LessTif threadsafe. The r6 Xt documentation describes
> what to do.
>
> >From memory (read this a couple of years ago), I think we
> need to add calls to ensure threadsafeness in a couple of
> standard places.
>
> The calls to place are XtAppLock and XtAppUnlock, see
> http://www.motifzone.com/resources/man/XtAppLock.html .
>
> Specific instructions seem to be in one of the O'Reilly
> books (see
> http://www.redhat.com/linux-info/gtk/gtk-list/1997-July/0173.html)
>
> Does anyone have it ? (I might, I'm not sure.)
>
> Uncle, how about giving it a try ?
>
> Danny
>
> Jon Fo wrote:
> >
> > >
> > > some folks who ported the java 116/i386/linux have used native threads
> > > to do threading. In their website they suggested that lesstif is not
> > > thread safe - which i suppose means that coordination of Xm calls
> > > between the independent threads just doesn't exist.
> > >
> > > it that true?, and if so are there any though processies going on to
> > > "make it so".
> > > gat
> > >
> > As I recall, Motif 1.2 is not thread safe, so if the port is expecting Motif 1.2.x,
> > then I don't see this as an issue. In fact, I believe the calls to Motif libraries
> > are (only) made from the AWT thread, so being thread-safe should not be an issue.
> > However, if you write native code that makes Motif calls, you're on your own.
> > I have a workaround that works in some situations.
> >
> > This is further corroborated by the fact that Java on Sun Solaris uses
> > Motif 1.2.x, which as I mentioned before, is probably not thread safe.
> >
