Kconfig.binfmt 7.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181
  1. config BINFMT_ELF
  2. bool "Kernel support for ELF binaries"
  3. depends on MMU && (BROKEN || !FRV)
  4. default y
  5. ---help---
  6. ELF (Executable and Linkable Format) is a format for libraries and
  7. executables used across different architectures and operating
  8. systems. Saying Y here will enable your kernel to run ELF binaries
  9. and enlarge it by about 13 KB. ELF support under Linux has now all
  10. but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
  11. because it is portable (this does *not* mean that you will be able
  12. to run executables from different architectures or operating systems
  13. however) and makes building run-time libraries very easy. Many new
  14. executables are distributed solely in ELF format. You definitely
  15. want to say Y here.
  16. Information about ELF is contained in the ELF HOWTO available from
  17. <http://www.tldp.org/docs.html#howto>.
  18. If you find that after upgrading from Linux kernel 1.2 and saying Y
  19. here, you still can't run any ELF binaries (they just crash), then
  20. you'll have to install the newest ELF runtime libraries, including
  21. ld.so (check the file <file:Documentation/Changes> for location and
  22. latest version).
  23. config COMPAT_BINFMT_ELF
  24. bool
  25. depends on COMPAT && BINFMT_ELF
  26. config ARCH_BINFMT_ELF_STATE
  27. bool
  28. config BINFMT_ELF_FDPIC
  29. bool "Kernel support for FDPIC ELF binaries"
  30. default y
  31. depends on (FRV || BLACKFIN || (SUPERH32 && !MMU) || C6X)
  32. help
  33. ELF FDPIC binaries are based on ELF, but allow the individual load
  34. segments of a binary to be located in memory independently of each
  35. other. This makes this format ideal for use in environments where no
  36. MMU is available as it still permits text segments to be shared,
  37. even if data segments are not.
  38. It is also possible to run FDPIC ELF binaries on MMU linux also.
  39. config CORE_DUMP_DEFAULT_ELF_HEADERS
  40. bool "Write ELF core dumps with partial segments"
  41. default y
  42. depends on BINFMT_ELF && ELF_CORE
  43. help
  44. ELF core dump files describe each memory mapping of the crashed
  45. process, and can contain or omit the memory contents of each one.
  46. The contents of an unmodified text mapping are omitted by default.
  47. For an unmodified text mapping of an ELF object, including just
  48. the first page of the file in a core dump makes it possible to
  49. identify the build ID bits in the file, without paying the i/o
  50. cost and disk space to dump all the text. However, versions of
  51. GDB before 6.7 are confused by ELF core dump files in this format.
  52. The core dump behavior can be controlled per process using
  53. the /proc/PID/coredump_filter pseudo-file; this setting is
  54. inherited. See Documentation/filesystems/proc.txt for details.
  55. This config option changes the default setting of coredump_filter
  56. seen at boot time. If unsure, say Y.
  57. config BINFMT_SCRIPT
  58. tristate "Kernel support for scripts starting with #!"
  59. default y
  60. help
  61. Say Y here if you want to execute interpreted scripts starting with
  62. #! followed by the path to an interpreter.
  63. You can build this support as a module; however, until that module
  64. gets loaded, you cannot run scripts. Thus, if you want to load this
  65. module from an initramfs, the portion of the initramfs before loading
  66. this module must consist of compiled binaries only.
  67. Most systems will not boot if you say M or N here. If unsure, say Y.
  68. config BINFMT_FLAT
  69. bool "Kernel support for flat binaries"
  70. depends on !MMU && (!FRV || BROKEN)
  71. help
  72. Support uClinux FLAT format binaries.
  73. config BINFMT_ZFLAT
  74. bool "Enable ZFLAT support"
  75. depends on BINFMT_FLAT
  76. select ZLIB_INFLATE
  77. help
  78. Support FLAT format compressed binaries
  79. config BINFMT_SHARED_FLAT
  80. bool "Enable shared FLAT support"
  81. depends on BINFMT_FLAT
  82. help
  83. Support FLAT shared libraries
  84. config HAVE_AOUT
  85. def_bool n
  86. config BINFMT_AOUT
  87. tristate "Kernel support for a.out and ECOFF binaries"
  88. depends on HAVE_AOUT
  89. ---help---
  90. A.out (Assembler.OUTput) is a set of formats for libraries and
  91. executables used in the earliest versions of UNIX. Linux used
  92. the a.out formats QMAGIC and ZMAGIC until they were replaced
  93. with the ELF format.
  94. The conversion to ELF started in 1995. This option is primarily
  95. provided for historical interest and for the benefit of those
  96. who need to run binaries from that era.
  97. Most people should answer N here. If you think you may have
  98. occasional use for this format, enable module support above
  99. and answer M here to compile this support as a module called
  100. binfmt_aout.
  101. If any crucial components of your system (such as /sbin/init
  102. or /lib/ld.so) are still in a.out format, you will have to
  103. say Y here.
  104. config OSF4_COMPAT
  105. bool "OSF/1 v4 readv/writev compatibility"
  106. depends on ALPHA && BINFMT_AOUT
  107. help
  108. Say Y if you are using OSF/1 binaries (like Netscape and Acrobat)
  109. with v4 shared libraries freely available from Compaq. If you're
  110. going to use shared libraries from Tru64 version 5.0 or later, say N.
  111. config BINFMT_EM86
  112. tristate "Kernel support for Linux/Intel ELF binaries"
  113. depends on ALPHA
  114. ---help---
  115. Say Y here if you want to be able to execute Linux/Intel ELF
  116. binaries just like native Alpha binaries on your Alpha machine. For
  117. this to work, you need to have the emulator /usr/bin/em86 in place.
  118. You can get the same functionality by saying N here and saying Y to
  119. "Kernel support for MISC binaries".
  120. You may answer M to compile the emulation support as a module and
  121. later load the module when you want to use a Linux/Intel binary. The
  122. module will be called binfmt_em86. If unsure, say Y.
  123. config BINFMT_MISC
  124. tristate "Kernel support for MISC binaries"
  125. ---help---
  126. If you say Y here, it will be possible to plug wrapper-driven binary
  127. formats into the kernel. You will like this especially when you use
  128. programs that need an interpreter to run like Java, Python, .NET or
  129. Emacs-Lisp. It's also useful if you often run DOS executables under
  130. the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
  131. <http://www.tldp.org/docs.html#howto>). Once you have
  132. registered such a binary class with the kernel, you can start one of
  133. those programs simply by typing in its name at a shell prompt; Linux
  134. will automatically feed it to the correct interpreter.
  135. You can do other nice things, too. Read the file
  136. <file:Documentation/binfmt_misc.txt> to learn how to use this
  137. feature, <file:Documentation/java.txt> for information about how
  138. to include Java support. and <file:Documentation/mono.txt> for
  139. information about how to include Mono-based .NET support.
  140. To use binfmt_misc, you will need to mount it:
  141. mount binfmt_misc -t binfmt_misc /proc/sys/fs/binfmt_misc
  142. You may say M here for module support and later load the module when
  143. you have use for it; the module is called binfmt_misc. If you
  144. don't know what to answer at this point, say Y.
  145. config COREDUMP
  146. bool "Enable core dump support" if EXPERT
  147. default y
  148. help
  149. This option enables support for performing core dumps. You almost
  150. certainly want to say Y here. Not necessary on systems that never
  151. need debugging or only ever run flawless code.