[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Java on AMD64 Question



well, what to do to get javaplugin for mozilla(-firefox) running?

Erik

On Son, 2005-02-27 at 21:26 +0100, Juergen Kreileder wrote:
> Anders Helmersson <anders.helmersson.utsikt@wasadata.net> writes:
> 
> > On Sun, 2005-02-27 at 10:04:21 -0800, tony mancill wrote:
> >> The plugin seems to work, but now when I start mozilla, I get the
> >> following:
> >>
> >> tony@honig:/usr/lib/mozilla/plugins$ mozilla grep: error while
> >> loading shared libraries: libc.so.6: cannot open shared object
> >> file: No such file or directory cut: error while loading shared
> >> libraries: libc.so.6: cannot open shared object file: No such file
> >> or directory sed: error while loading shared libraries: libc.so.6:
> >> cannot open shared object file: No such file or directory
> >
> > I have had the same problem and it seems to be caused by the line
> > export LD_ASSUME_KERNEL=2.2.5
> > in the set_jvm_vars () in /usr/bin/firefox
> 
> Likely, I don't have a Debian/amd64 installation but AFAIK it's
> NPTL-only.  With LD_ASSUME_KERNEL=2.2.5 glibc tries to load
> LinuxThreads instead and that isn't available.
> 
> > I am not sure if this is related to our installations or if it is a
> > bug in the firefox startup script.
> 
> The script should be patched for amd64, all existing amd64 VMs work
> fine with NPTL
> 
> > In addition, I get problems when using the java blackdown plugin
> > with some applications on the web (a secure login function) the java
> > application fails sometimes with a segfault and sometimes it
> > produces the attached error log ("An unexpected exception has been
> > detected in native code outside the VM").
> 
> Mozilla's OJI interface still has 64-bit issues.  I've written fixes
> for Sun over a year ago but it looks like they still haven't pushed
> them into Mozilla.
> 
> 
>         Juergen
> 
> -- 
> Juergen Kreileder, Blackdown Java-Linux Team
> http://www.blackdown.org/java-linux/java2-status/
> 
> 



Reply to: