README 2.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
  1. uClibc - a Small C Library for Linux
  2. Erik Andersen <andersen@codepoet.org>
  3. uClibc (aka µClibc/pronounced yew-see-lib-see) is a size-optimized
  4. implementation of the standard C library. It is primarily designed
  5. for developing embedded Linux systems. It is much smaller then the
  6. GNU C Library, but nearly all applications supported by glibc also
  7. work perfectly with uClibc. Porting applications from glibc to
  8. uClibc typically involves just recompiling the source code. uClibc
  9. even supports shared libraries and threading. It currently runs on
  10. standard Linux and MMU-less (also known as µClinuxClinux) systems
  11. with support for ARM, i386, h8300, m68k, mips, mipsel, PowerPC, SH,
  12. SPARC, and v850 processors.
  13. For installation instructions, see the file INSTALL.
  14. This distribution contains a wrapper for gcc and ld that allows you
  15. to use existing toolchains that were targetted for glibc. See
  16. extra/gcc-uClibc/ for information.
  17. uClibc strives to be standards compliant, which means that most
  18. documentation written for functions in glibc also apply to uClibc
  19. functions. However, many GNU extensions are not supported because
  20. they have not been ported, or more importantly, would increase the
  21. size of uClibc disproportional to the added functionality.
  22. Additional information (recent releases, FAQ, mailing list, bugs,
  23. etc.) can be found at http://www.uclibc.org/.
  24. uClibc may be freely modified distributed under the terms of the
  25. GNU Library General Public License, which can be found in the
  26. file COPYING.LIB.
  27. Please Note:
  28. There is an unwholesomely huge amount of code out there
  29. that depends on the presence of GNU libc header files.
  30. We have GNU libc header files. So we have committed a
  31. horrible sin in uClibc. We _lie_ and claim to be GNU
  32. libc in order to force these applications to work as their
  33. developers intended. This is IMHO, pardonable, since
  34. these defines are not really intended to check for the
  35. presence of a particular library, but rather are used to
  36. define an _interface_. Some programs (such as GNU
  37. binutils) are especially chummy with glibc, and need this
  38. behavior disabled by adding CFLAGS+=__FORCE_NOGLIBC