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

Re: Release-critical Bugreport for December 7, 1998

In article <19981207214438.A5784@cs.leidenuniv.nl>, Wichert Akkerman <wakkerma@debian.org> writes:
>> > Package: libguile3
>> > Maintainer: David N. Welton <davidw@efn.org>
>> > 30102 missing shared library
>> > 30107 just another package bitten by __register_frame_info

>> If I'm not mistaken these and 29479 and 30336 are the same
>> bug. Could s/o please merge them?

> Better yet, close them. The problem was the libc6 disaster which has
> been fixed now.

That would seem to be premature to me:

> ldd /usr/X11R6/bin/siag 
        libm.so.6 => /lib/libm.so.6 (0x40011000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x4002a000)
        libguile.so.3 => /usr/lib/libguile.so.3 (0x40059000)
        libqthreads.so.0 => /usr/lib/libqthreads.so.0 (0x400c5000)
        libtcl8.0.so.1 => /usr/lib/libtcl8.0.so.1 (0x400c7000)
        libdl.so.2 => /lib/libdl.so.2 (0x4012f000)
        libXpm.so.4 => /usr/X11R6/lib/libXpm.so.4 (0x40132000)
        libdb.so.2 => /lib/libdb.so.2 (0x40140000)
        libXaw.so.6 => /usr/X11R6/lib/neXtaw/libXaw.so.6 (0x4014e000)
        libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x401a4000)
        libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x401b6000)
        libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x401fe000)
        libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x40208000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x4021d000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40229000)
        libc.so.6 => /lib/libc.so.6 (0x402cc000)
        libreadline.so.2 => /lib/libreadline.so.2 (0x40371000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
        libncurses.so.4 => /lib/libncurses.so.4 (0x4039c000)
> /usr/X11R6/bin/siag 
/usr/X11R6/bin/siag: error in loading shared libraries
/usr/lib/libguile.so.3: undefined symbol: __register_frame_info

Doesn't this show that the bug is still present?

.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>

Reply to: