Re: xlib6/xlib6g
> > Xlib6 is linked against libc5, while xlib6g is linked against libc6. For
> > libc6 development you want the "g" version. They conflict for, what should
> > be, obvious reasons.
>
> The shared libs don't conflict.
xlib6g does conflict with old versions of xlib6 (i.e., the one
in bo). This is, (as I'm sure everybody on this thread knows,
except the original poster) because xlib6g installs it's libraries
in the same directory as the old versions of xlib6 do, and they would
thus be overwritten. Then no libc5 Xapp would work any more.
Just first upgrade your xlib6 to the one in hamm, then install xlib6g.
>
> > Xlib6g "breaks" those X programs that are still linked against libc5. As
> > these programs get rebuilt the problems will go away.
>
> Only those that were incorrectly linked with an -rpath flag.
Yes, and only very few X apps were linked with -rpaht, it seems.
So far, I only know of fvwm2, old emacs and gv versions that were
broken.
--
joost witteveen, joostje@debian.org
#!/usr/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
#what's this? see http://www.dcs.ex.ac.uk/~aba/rsa/
--
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: