** From: Casiraghi Luigi <[EMAIL PROTECTED]>
> I've installed jdk1.1.6v2 on my linux box following
> the README and the FAQ instructions but as soon as
> I launched the example:
> I received a SIGSEGV 11* segmentation violation.
> Linux Slackware 3.0 (kernel 2.0.0)
> jdk1.1.6v2
> libc5 (I upgraded to libc to libc5.4.44 and also ld as recommended)
> ldconfig: version 1.9.9
> Another effect is the creation of a core file
> of about 19Mb on my HD :-(.
I ran into the same thing after installing glibc2.0.6, libc5.4.44, and
jdk1.1.6v2 on my Slackware (2.0.30) system. The Java-Linux faq
mentioned a possible bug in ldconfig1.9.9, and I also found other
references to people upgrading to a newer glibc (2.0.7-13). Of
course, I had already wiped out my older ldconfig :-), so I went out
looking for replacements.
I found an older ldconfig easily enough, but it turned out that the
newer glibc was only available in RPM format, and wasn't easy to find.
I finally found it at ftp.redhat.com - not in /pub/glibc like you
might expect, but in /pub/redhat/redhat-5.1/SRPMS/SRPMS. RPM's and
Slackware don't seem to mix, but this one is just source, so 'rpm -i'
will just install the source tar-ball and the patches in some directory
that you'll probably need to create after it fails the first time. :-)
Anyway, I decided to upgrade glibc before downgrading ldconfig.
Upgrading glibc did the trick, so I left ldconfig alone at 1.9.9. One
slightly confusing thing: the rpm includes version 2.0.6 of the crypt
libraries, instead of calling it 2.0.7-13 like the rest of the
package. This cost me some time looking around for a matching set,
but in the end it worked just fine as it was.
Regards,
Aaron
--
Aaron Baugher - [EMAIL PROTECTED]
Extreme Systems Consulting - http://haruchai.rnet.com/esc/
CGI, Perl, Java, and Linux/Unix Administration
