Config.in.arch 3.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131
  1. #
  2. # For a description of the syntax of this configuration file,
  3. # see extra/config/Kconfig-language.txt
  4. #
  5. config ARCH_ANY_ENDIAN
  6. bool
  7. config ARCH_BIG_ENDIAN
  8. bool
  9. config ARCH_LITTLE_ENDIAN
  10. bool
  11. if ARCH_ANY_ENDIAN
  12. choice
  13. prompt "Target Processor Endianness"
  14. help
  15. This is the endianness you wish to use. Choose either Big
  16. Endian, or Little Endian.
  17. config ARCH_WANTS_BIG_ENDIAN
  18. bool "Big Endian"
  19. select ARCH_BIG_ENDIAN
  20. config ARCH_WANTS_LITTLE_ENDIAN
  21. bool "Little Endian"
  22. select ARCH_LITTLE_ENDIAN
  23. endchoice
  24. endif
  25. # if the arch only supports one endian, just display the setting
  26. if !ARCH_ANY_ENDIAN && ARCH_LITTLE_ENDIAN
  27. comment "Using Little Endian"
  28. endif
  29. if !ARCH_ANY_ENDIAN && ARCH_BIG_ENDIAN
  30. comment "Using Big Endian"
  31. endif
  32. config ARCH_HAS_NO_MMU
  33. bool
  34. if ARCH_HAS_NO_MMU
  35. comment "Target CPU lacks a memory management unit (MMU)"
  36. endif
  37. config ARCH_HAS_MMU
  38. bool "Target CPU has a memory management unit (MMU)"
  39. depends !ARCH_HAS_NO_MMU
  40. default y
  41. help
  42. If your target CPU does not have a memory management unit (MMU),
  43. then answer N here. Normally, Linux runs on systems with an MMU.
  44. If you are building a uClinux system, answer N.
  45. Most people will answer Y.
  46. config ARCH_USE_MMU
  47. bool "Do you want to utilize the MMU?"
  48. depends on ARCH_HAS_MMU
  49. default y
  50. help
  51. If your target CPU has a MMU, and you wish to actually utilize it,
  52. then answer Y here. Normal Linux requires an MMU.
  53. If you're unsure, answer Y.
  54. config UCLIBC_HAS_FLOATS
  55. bool "Enable floating point number support"
  56. default y
  57. help
  58. This option allows you to entirely omit all floating point number
  59. support from uClibc. This will cause floating point functions like
  60. strtod() to be omitted from uClibc. Other floating point functions,
  61. such as printf() and scanf() will still be included in the library,
  62. but will not contain support for floating point numbers.
  63. Answering N to this option can reduce the size of uClibc. Most people
  64. will answer Y.
  65. config UCLIBC_HAS_FPU
  66. bool "Target CPU has a floating point unit (FPU)"
  67. depends on UCLIBC_HAS_FLOATS
  68. default y
  69. help
  70. If your target CPU does not have a Floating Point Unit (FPU) or a
  71. kernel FPU emulator, but you still wish to support floating point
  72. functions, then uClibc will need to be compiled with soft floating
  73. point support (-msoft-float). If your target CPU does not have an
  74. FPU or an FPU emulator within the Linux kernel, then you should
  75. answer N.
  76. Most people will answer Y.
  77. config UCLIBC_HAS_SOFT_FLOAT
  78. bool
  79. depends on UCLIBC_HAS_FLOATS && !UCLIBC_HAS_FPU
  80. default y
  81. config DO_C99_MATH
  82. bool "Enable full C99 math library support"
  83. depends on UCLIBC_HAS_FLOATS
  84. default n
  85. help
  86. If you want the uClibc math library to contain the full set C99
  87. math library features, then answer Y. If you leave this set to
  88. N the math library will contain only the math functions that were
  89. listed as part of the traditional POSIX/IEEE 1003.1b-1993 standard.
  90. Leaving this option set to N will save around 35k on an x86 system.
  91. If your applications require the newer C99 math library functions,
  92. then answer Y.
  93. config KERNEL_SOURCE
  94. string "Linux kernel header location"
  95. default "/usr/src/linux"
  96. help
  97. The kernel source you use to compile with should be the same as the
  98. Linux kernel you run your apps on. uClibc doesn't even try to achieve binary
  99. compatibility across kernel versions. So don't expect, for example, uClibc
  100. compiled with Linux kernel 2.0.x to implement lchown properly, since 2.0.x
  101. can't do that. Similarly, if you compile uClibc vs Linux 2.4.x kernel headers,
  102. but then run on Linux 2.0.x, lchown will be compiled into uClibc, but won't
  103. work at all. You have been warned.
  104. config UCLIBC_UCLINUX_BROKEN_MUNMAP
  105. bool
  106. depends on !ARCH_USE_MMU
  107. default y
  108. config EXCLUDE_BRK
  109. bool
  110. depends on !ARCH_USE_MMU
  111. default y
  112. config HAVE_DOT_CONFIG
  113. bool
  114. default y