关于glibc与BSD libc的比较

unix-ilke系统真的是百家争鸣。之前知道很多很多不同的发行版。也曾经因为在solaris下做过一些开发，从而接触过BSD体系的皮毛。最近一直在做Android下的开发，稍微关注了一下其中的Bionic，一如google申明的它是植根于BSD的libc体系的。因为大部分的工作都是使用glibc进行开发，处于好奇关注了下两者的区别。

以下内容是从一个邮件组里面所引用,因为是比较老的信息,只能作为参考。如果需要做port的考量或者做搭建新系统的考量，一定还得对没项的最新情况进行调查。

总体而言，两者针对的平台体系不太一样，或多或少会有一些底层interface的差别。对我们大部分的开发者而言，是在某一平台体系下开发时，如果需要用到其它体系下有的好的功能或者interface，就需要查找考量是做porting还是应该从头实现！！

glibc vs BSD libc

http://lists.debian.org/debian-bsd/2003/01/msg00013.html

Why is it important for debian BSD to sum up the differences in BSD libc and glibc?
What I have learned from this thread (and from porting apps from linux to NetBSD and Solaris):

- there are differences between the libcs of these systems.
- sometimes they hurt during ports, most of the time, they don´t hurt
- the dominance of glibc-based linux has forced IBM and SUN to supply linux programming
  interfaces. This might happen in the BSD world in the future.
- for the debian/BSD project on the sparc it seems to be better to stick to BSD libc
  (we keep in track with alpha and intel ports)

So, coming back to the main topic: how did the NetBSD/intel people overcome these difficulties
caused by bsd libc/glibc?

1.
License
glibc :