Date: Sun, 2 Dec 2001 01:46:15 +1030 From: Greg Lewis <glewis@eyesbeyond.com> To: Bill Huey <billh@gnuppy.monkey.org> Cc: Joe Kelsey <joe@zircon.seattle.wa.us>, freebsd-java@FreeBSD.ORG Subject: Re: Plugin Status Message-ID: <20011202014615.A36600@misty.eyesbeyond.com> In-Reply-To: <20011130141837.A6065@gnuppy>; from billh@gnuppy.monkey.org on Fri, Nov 30, 2001 at 02:18:37PM -0800 References: <15367.52862.957201.411578@zircon.zircon.seattle.wa.us> <20011130141837.A6065@gnuppy>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 30, 2001 at 02:18:37PM -0800, Bill Huey wrote: > On Fri, Nov 30, 2001 at 10:22:54AM -0800, Joe Kelsey wrote: > > I am supremely tired of fighting with Motif bugs. The plugin currently > > loads, reads and responds to commands from Mozilla, and then dies as it > > tries to create a window within Mozilla's window. Ouch. > > I have tried it with both Open Motif and LessTif. LessTif is much > > better, since it has better diagnostics by default and fewer blatant > > bugs. Open Motif is such a hog--poorly written and littered with > > blatant programming errors. Sigh. > > Did you try and talk to the OpenMotif folks ? They're pretty helpful and > are willing to fix bugs quickly from my experiences. Interestingly though, the Open Motif port hasn't been updated in quite a long time, so if they're fixing bugs they don't seem to be releasing the patches :(. Lesstif on the other hand is still actively making releases, although the port was out of data last time I looked. > > I plan to put aside the plugin for the time being and switch over to > > working on HotSpot. The last time I switched gears, from trying to > > debug green threads to using Bill's native threads, the plugin operation > > suddenly improved greatly. I am hoping that something to do with > > HotSpot may have a similar effect on the plugin operation. > > Hehe, that's good to hear. Geez, I hope folks realize how significant > this is for the overall port. It basically means we are "for real" now, > IMO. ;-) Well, I think we've been for real since at least the last patchset personally :). Seeing the native threads progress is great though, thanks Bill! This paves the way for a 1.4 port. > > HotSpot is organized into system-specific directories. The current > > split is between solaris and linux, with most files duplicated in the > > separate hirearchies. After seeing some of the horrible linuxisms > > contained in the current code base, I am going to go and base the bsd > > code base for HotSpot on solaris and move forward from there. Every > > time I look at something done for Linux, I get sick. I may refer to the > > linux code if I need a laugh, but otherwise I plan to more or less > > ignore it. > > Yes, it is. It's a pretty standard about machine specific conventions > like with all JIT compilers. I'd be worried about JIT block linkage and > calling conventions within HotSpot itself since GCC is going through > significant changes and it's unclear how the -stable compiler will behave > with HotSpot. It's a pretty self contained system, but having it written > in C++ is potentially a serious problem considering that GCC is constantly > changing core C++ internals every minor revision or so it seems. I believe you'll find the C++ internals have stabilised with gcc3. Unfortunately this isn't the compiler available on -stable :(. However, we're far better off still than say RedHat 7.x which I have to deal with at work and its broken gcc 2.96. > Good Luck and report back errors either publically or privately. ;-) Preferably publicly :) > > For now, I am recompiling LessTif with debugging enabled in one last > > effort at finding bugs. Then it is on to HotSpot. > > I recommend bailing on LessTif and work with the OpenMotif folks. Post > a stack trace to them and they should be able to give you some solid > pointers on the subject and possibly build a prepatch for you that fixes > the problem. Tell them who you are and what your relationship is to this > project, how significant it is for the BSD community and I'm sure somebody > will get back to you on the subject. Definitely try and people network > with people as much as you can when doing ports like this which are too > large for a single person to fully understand. That's when talking to > other folks really facilitates the development process. True. The job is too big to get a handle on all the pieces yourself. I apologise for not helping out more lately, work is hammering me at the moment. > I might be taking a job soon as a WINE engineer. If that's the case, then > I'll be dropping out of this development group and until my next development > cycle. Well good news for you, not so good for Java development. Thanks for the work you've done Bill! -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Phone : (801) 765 1887 Information Technology Web : http://www.eyesbeyond.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011202014615.A36600>