Re: xlib6g and emacs (and others)
-----BEGIN PGP SIGNED MESSAGE-----
On 9 Sep 1997, Erv Walter wrote:
> As soon as I install xlib6g, emacs core dumps and ldd reports this:
>
> libXaw.so.6 => /usr/X11R6/lib/libXaw.so.6 (0x4000d000)
> libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x40045000)
> libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x40057000)
> libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x4009f000)
> libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x400a8000)
> libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x400bd000)
> libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x400c9000)
> libncurses.so.3.0 => /lib/libncurses.so.3.0 (0x4016d000)
> libm.so.5 => /lib/libm.so.5 (0x401a9000)
> libc.so.5 => /lib/libc.so.5 (0x401b2000)
> libc.so.6 => /lib/libc.so.6 (0x4026e000)
> ld-linux.so.2 => /lib/ld-linux.so.2 (0x4030c000)
>
>
> Now, I don't know if emacs (and 90% of other executables) is broken,
> or if there is a problem with xlib6g or if ld.so is not working.
>
> In anycase. Something is wrong. Note, however, that some programs
> work fine. xterm works fine. ldd reports it is linked with the
> libc5-compat libs even with xlib6g installed
I suspect it may be a problem that the libc5-based xlib packages still
seem to be statically linked rather than linked with libc5. At least
that's what ldd reports. I haven't done much investigating yet myself.
- --
| In order to live freely and happily,
Scott K. Ellis | you must sacrifice boredom.
storm@gate.net | It is not always an easy sacrifice.
| -- Illusions
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv
iQCVAwUBNBVRp6Ck2fENdzpVAQGfdAP/YeQXeFpaGFE+r/8gyodIT69xyvKgwTTO
lQdAltNj2eWDEcEYZdcLwuwxIISP+9gYiVD7oaMmisdWm2FG99ynPh+ssgy8TN1U
9IJZo8+F+M+W+LKb6mv0TegUpubt7yOMGiAuxF1qQt6xa/BmZQZTqnUNvqFH3DWo
nUMVlohHhX0=
=nLmt
-----END PGP SIGNATURE-----
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . Trouble?
e-mail to templin@bucknell.edu .
Reply to: