On starting mozilla, the following message appears: LoadPlugin: failed to initialize shared library /usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so [Cannot open "/usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so"] This is due to the lack of the Java Development kit. The port installs the following symlink, but it doesn't check for the existence of the library: /bin/ln -sf /usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so /usr/X11R6/lib/mozilla-devel/plugins/libjavaplugin_oji.so There is no indication of why this happens, or what to do about it. Fix: The problem here seems to be that the Java library needs to be downloaded manually, due to the strange license requirements. I'd suggest: 1. Only create the symlink if the target file /usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so actually exists. 2. If it doesn't exist, print instructions for how to install it, and what the consequences will be if you don't. How-To-Repeat: Install mozilla or mozilla-devel on a clean system.
Hi, On Thu, Sep 19, 2002 at 11:29:20AM +0930, Greg Lehey wrote: > >Fix: > > The problem here seems to be that the Java library needs to be > downloaded manually, due to the strange license requirements. > I'd suggest: > > 1. Only create the symlink if the target file > /usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so > actually exists. > 2. If it doesn't exist, print instructions for how to install > it, and what the consequences will be if you don't. Why is this a problem? Mozilla works fine, and it means that Java plugins just start working if and when you install the JDK. If the symlink is conditioned then you have to manually install it if you install the JDK after mozilla... The port/package should probably have a message though that tells you need to install the JDK if you want Java support. Regards, -Jeremy -- FreeBSD - Because the best things in life are free... http://www.freebsd.org/
On Thursday, 19 September 2002 at 9:57:45 +0200, Jeremy Lea wrote: > Hi, > > On Thu, Sep 19, 2002 at 11:29:20AM +0930, Greg Lehey wrote: >>> Fix: >> >> The problem here seems to be that the Java library needs to be >> downloaded manually, due to the strange license requirements. >> I'd suggest: >> >> 1. Only create the symlink if the target file >> /usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so >> actually exists. >> 2. If it doesn't exist, print instructions for how to install >> it, and what the consequences will be if you don't. > > Why is this a problem? Because it takes a lot of time for anybody not intimately involved with the installation to find out what is going on. For non-developers, it would probably mean that they would give up on it. > Mozilla works fine, and it means that Java plugins just start > working if and when you install the JDK. If the symlink is > conditioned then you have to manually install it if you install the > JDK after mozilla... > > The port/package should probably have a message though that tells you > need to install the JDK if you want Java support. Well, yes, that's what I said. Agreed, it might make sense to do the symlink in either case, and explain in the message what is going to happen. Greg -- See complete headers for address and phone numbers
Responsible Changed From-To: freebsd-ports->gnome over to maintainer
State Changed From-To: open->closed Greg, thanks for your comments. I have added a pkg-message to the Mozilla ports explaining to users how to get Java working.