How would adding a function break compatibility? If that were the case, no new function could ever be added to any library without breaking compatibility with the old version.
Posted May 7, 2009 9:25 UTC (Thu) by nix (subscriber, #2304)
[Link]
It breaks compatibility in that adding a function to eglibc means that you
can no longer reliably replace eglibc with glibc. (Whether this is
problematic is another matter.)
Here's hoping strlcat gets in
Posted May 7, 2009 12:05 UTC (Thu) by epa (subscriber, #39769)
[Link]
Obviously, fixing the ARM bug linked in the article also means that you can no longer reliably replace eglibc with glibc, since this would break (or at least break the build) on previously working ARM systems. I think your definition of compatibility is a bit too strict.