On Thu, 2003-02-20 at 10:08, Chris Lambert wrote: > Nicholas Hockey <[EMAIL PROTECTED]> wrote: > > > > Its a known bug with mozilla and jre, you have to compile mozilla with > > gcc2 and it will work fine > > > > Is it a bug? Or is it just the way it works? > > More precisely, you have to compile mozilla and java with the same version > of GCC. So, you can also compile java from source with gcc 3 (assuming > mozilla is compiled with gcc 3).
Another way. emerge sync ACCEPT_KEYWORDS="~x86" emerge -u blackdown-jre java-config --set-system-vm=blackdown-jre-1.4.1 env-update emerge unmerge/usr/portage/dev-java/blackdown-jre/blackdown-jre-1.3.1-r9.ebuild emerge -i dev-java/blackdown-jre-1.3.1-r9 cd /usr/lib/mozilla/plugins rm javaplugin_oji.so ln -s /opt/blackdown-jre-1.4.1/plugin/i386/mozilla/javaplugin_oji.so Remember to update your environment. This way you 1) emerge the masked blackdown jre 1.4.1 (compiled with gcc 3.2) 2) unmerge the previous version (facultative step) 3) inject the previous version (so that portage thinks it's still here and doesn't try to downgrade at every update (facultative step) 3) set the system vm to the newer version 4) delete any existing plugin from mozilla plugin dir 5) link mozilla to the new plugin It does work very well for me. You can do the same thing with the jdk. Take these infos with a grain of salt, I've written them down but I can't check them right now. -- Arturo di Gioia web: http://www.ing.unitn.it/~digioia/ PGP public key: http://www.ing.unitn.it/~digioia/files/adg_gpg_pub.asc Registered Linux user #230853 (http://counter.li.org). Instructions for using my e-mail address: http://netiquette.info/ -- [EMAIL PROTECTED] mailing list
