Kconfig.binfmt 7.6 KB

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