Rhon, Joe, >>does, it hits the bad library (/lib/i686/libc.so6) and disappears >>on me... >> So it may not be a prob with Java at all...still, after installing >>that RPM I pointed you to, you should have jre1.5, not 1.4. That's >>weird. > >Don't know if this was already brought up (haven't been following this >thread that closely)... > >I don't have Java installed at the moment, but when I installed it in >10.0, it didn't install to one of the standard binary locations >(/bin, /usr/bin, /usr/local/bin). I either had to add the non-standard >location to the path (which I didn't like the idea of), or symlink the >executables I needed into one of the standard locations. I think I >created symlinks in /usr/local/bin to the Java binary directory. I >think I also had to create links in /usr/local/lib to Java libraries.
The problem is not java itself, I have become sure of that. Java is well-behaved enough to follow the PATH and the JAVA_HOME environment variables. The problem lies in a file called libc.so.6 which is a symlink to libc-2.3.5.so. This file is located in /lib/i686 and also in /lib. Earlier on it even existed in /lib/tls but I mv'd that out of the way. Things crash on a function call NULL towards the offending library file. I wonder if removing the i686 subdir would make things work, as the same files exist in /lib (be it different versions/builds, as they are a bit smaller). /lib/i686: [EMAIL PROTECTED] i686]$ ls -l libc* -rw-r--r-- 1 root root 1234464 Aug 30 2005 libc-2.3.5.so lrwxrwxrwx 1 root root 17 Apr 9 13:51 libc.so.6 -> libc-2.3.5.so /lib: [EMAIL PROTECTED] lib]$ ls -l libc* -rwxr-xr-x 1 root root 1197600 Aug 30 2005 libc-2.3.5.so* lrwxrwxrwx 1 root root 13 Feb 1 18:48 libc.so.6 -> libc-2.3.5.so* (snipped out the offending library) See what I mean? Paul ____________________________________________________ Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com Join the Club : http://www.mandrivaclub.com ____________________________________________________
