Re: recompile needed for xlib6g
On Oct 09, Edward Betts <email@example.com> wrote:
>> I don't know that for sure. But we do know there are binary-level issues
>> between slink libc6 and potato libc6. Since people will need to recompile
>> against a newer libc6 anyway, why not add the new xlib6g to the mix?
>Why will people NEED to recompile against a newer libc6?
Most people does not NEED, but some packages when compiled against glibc
2.1 get new functionalities (like IPv6).
(Shameless self advertisement: for a simple IPv4/IPv6 implementation look
at my whois 4.0 package.)