Dale Scheetz <firstname.lastname@example.org> writes:
> 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 "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.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to email@example.com .