gcc-3.1 libcj issues

[Adam Megacz]

Tom Tromey <tromey@redhat.com> writes:
> Yes, please report these.  This gets a little out of our hands.  It
> would be too bad if we couldn't support Darwin in this release, but we
> might be forced that way.  Let's at least give it a try though.

Hey, sorry I haven't been tracking this; did we ever come up with a
solution for how to let the GC stop all threads on Darwin? It had
something to do with Darwin not having pthread_kill()...

I'm using HotSpot for XWT on OSX (since it ships with the OS, so it's
guaranteed to be there), but I'd like to move to GCJ eventually.

  - a

-- 
"If I put copyrighted material into the 'chewy nougat center', I can
 claim the crunchy chocolate coating is an 'Access Control
 Mechanism'."                                     --lynx_user_abroad