Date: Wed, 20 Feb 2002 18:06:35 +1030 From: Greg Lewis <glewis@eyesbeyond.com> To: Jeremy Lea <reg@FreeBSD.ORG> Cc: freebsd-java@FreeBSD.ORG Subject: Re: Mozilla plugin and native JDK 1.3.1p6. Message-ID: <20020220180634.E87848@misty.eyesbeyond.com> In-Reply-To: <20020216220026.D60480@shale.csir.co.za>; from reg@FreeBSD.ORG on Sat, Feb 16, 2002 at 10:00:26PM %2B0200 References: <20020215150421.A50739@shale.csir.co.za> <20020215220554.H20348@tigerfish2.my.domain> <20020216220026.D60480@shale.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
Late reply as I was away for the President's Day weekend... On Sat, Feb 16, 2002 at 10:00:26PM +0200, Jeremy Lea wrote: > On Fri, Feb 15, 2002 at 10:05:54PM -0600, Bruce Burden wrote: > > What version of Mozilla do you have? I have mozilla-0.9.7_2,1, > > and jdk1.3.1 works w/out a problem. (Once the port was updated, > > that is). > > 0.9.8_1,1. I'm worried that this might be one of the changes I made to the > port. It looks like there's no simple answer, and I'm going to have to > debug things... > > This was on -CURRENT. I'm going to build the JDK and Mozilla with debugging > on -STABLE now, and see if I get the same behaviour, and back things out to > 0.9.7 on -CURRENT and see if that works. > > Is this with green threads or native threads? The port failed to build with > native threads for me... There is no way native threads will build on -CURRENT. The whole implementation currently uses private parts of the pthread library which have changed between -STABLE and -CURRENT. Ok, you could get it to build if you had the -STABLE source code as well, but it would immediately crash and burn. > I posted another message in response to my original, with some debugging > output which suggests that the plugin is not being correctly linked with > libxpcom from Mozilla. > > Something which concerns me greatly is that the plugin seems to be linked > with references to all sorts of Mozilla things, but I didn't have Mozilla > installed at the time I built it... This probably means that the plugin is > being built with it's own copy of a lot of private headers, which are out of > date for 0.9.8. There are two things here. Firstly, the plugin does use a bunch of Mozilla headers. Most of these are quite old, but others I updated (to 0.9.5 most recently I think). I couldn't update all of them as Mozilla had turned into a header dependency nightmare (at least at that point). Secondly, the plugin uses NSPR, so that may also look like its using bits of Mozilla. > I guess we're going to have to look into building the plugin as a seperate > port, which depends on Mozilla. It doesn't need to depend on Mozilla, NSPR should be sufficient. We can certainly update some more of the Mozilla headers if they can be untangled. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology 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?20020220180634.E87848>