Perl 5.004.04-3 Coredump problem SOLVED!!!

[Neilen Marais <brick@cryogen.com>]

HI all

You might remember me moaning about adduser and some other things
breaking when I upgrade from the bo perl 5.003summin to the newest hamm
perl.

I did not get much helpful respone, because I assume the problem is
rather obscure.  So I did a bit of investigating, and I seem to have
narrowed down the problem to the libraries perl is trying to use.  If I
type ldd perl5.00404 I get this:

brick@brickbox[ttyp4]: ~$ ldd /usr/bin/perl5.00404
        libnsl.so.1 => /lib/libnsl.so.1 (0x4000f000)
        libgdbm.so.1 => /opt/kde/lib/libgdbm.so.1 (0x40015000)
        libdb.so.2 => /lib/libdb.so.2 (0x4001b000)
        libdl.so.2 => /lib/libdl.so.2 (0x40029000)
        libm.so.6 => /lib/libm.so.6 (0x4002c000)
        libc.so.6 => /lib/libc.so.6 (0x40045000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
        libcrypt.so.1 => /lib/libcrypt.so.1brick@brickbox[ttyp4]: ~$
        libc.so.5 => /lib/libc.so.5 (0x40116000)

Now the libc5 bit must obviously be wrong... So I thaught, perhaps it
had something to do with libcrypt.so.1 using libc5, but if I type ldd
libctrypt.so.1 I get this:

brick@brickbox[ttyp4]: ~$ ldd /lib/libcrypt.so.1
        libc.so.6 => /lib/libc.so.6 (0x40030000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00000000)

which to me looks quite peachy

But then, spurred on by writing this E-Mail, I suddenly find the
solution....  Looking at the ldd perl bit I see

libgdbm.so.1 => /opt/kde/lib/libgdbm.so.1 (0x40015000)

/opt/kde/lib!!!!?? How dit THAT happen?  Anyway, check /etc/ld.so.conf,
nothing there.  Do set | grep LD, and VOILA <sp?>, it was set in my
LDCONFIG.

Now of course I had no idea that the env var was looked at before
ld.so.conf, or why on EARTH the kde package includes a libgdbm.so.1!! 
Well, at least I learnt something today :) (actually stricty speaking
yesterday as it was just midnight)

As you might guess, this is the deb package done by KDE, not the debian
one, which I installed because I was still using bo at the time.  And
since most people do I assume run the Debian KDE package (if they run
KDE), they never ran accross this problem.

I solved the problem by removing /opt/kde/lib from LDCONFIG, and
putting it at the end of /etc/ld.so.conf.

On another note, while this might not be a terribly common problem,
perhaps the maintainer of the libc5 to libc6 mini-HOWTO would like to
add the possibility of, and solution to this problem to it?

Cheers
Neilen (Happier Debian user than ever :)

----------------------------------
E-Mail: Neilen Marais <brick@cryogen.com>
Date: 16-Jan-98
Time: 23:34:29

This message was sent by XFMail
----------------------------------


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .