control 1.9 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647
  1. Source: uclibc
  2. Section: devel
  3. Priority: optional
  4. Maintainer: David Schleef <ds@schleef.org>
  5. Build-Depends: debhelper, bzip2, kernel-source-2.4.18
  6. Standards-Version: 3.5.6
  7. Package: libuclibc-dev
  8. Section: devel
  9. Architecture: arm i386 m68k mips mipsel powerpc sh sparc
  10. Depends: libuclibc0 (= ${Source-Version})
  11. Description: A small implementation of the C library
  12. uClibc is an implementation of the standard C library that is
  13. much smaller than glibc, which makes it useful for embedded
  14. systems. This package includes header files and development
  15. libraries necessary to compile applications that use uClibc.
  16. Package: libuclibc0
  17. Section: libs
  18. Architecture: arm i386 m68k mips mipsel powerpc sh sparc
  19. Depends:
  20. Description: A small implementation of the C library
  21. uClibc is an implementation of the standard C library that is
  22. much smaller than glibc, which makes it useful for embedded
  23. systems. This package provides only the run-time libraries.
  24. .
  25. The Debian binary packages for uClibc do not provide the necessary
  26. components for using uClibc as the primary library on a system,
  27. as might be done for an embedded system.
  28. Package: uclibc-toolchain
  29. Section: devel
  30. Architecture: arm i386 m68k mips mipsel powerpc sh sparc
  31. Depends: gcc|c-compiler, binutils, ${shlibs:Depends}
  32. Recommends: libuclibc-dev
  33. Conflicts: uclibc-gcc
  34. Replaces: uclibc-gcc
  35. Description: A compiler wrapper for uClibc
  36. This package includes utilities that function as a toolchain for
  37. compiling with uClibc instead of the native libc. The utilities
  38. have names such as powerpc-uclibc-gcc (depending on the architecture),
  39. and should behave identically to the base utilities, except that
  40. they use headers and libraries provided in the libuclibc-dev
  41. package. Most utilities are symbolic links to the correct underlying
  42. utility, although gcc and ld are implemented as wrapper binaries that
  43. call gcc and ld with the necessary arguments and command line options.