Kconfig.binfmt 5.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139
  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 && MMU
  26. config BINFMT_ELF_FDPIC
  27. bool "Kernel support for FDPIC ELF binaries"
  28. default y
  29. depends on (FRV || BLACKFIN || (SUPERH32 && !MMU))
  30. help
  31. ELF FDPIC binaries are based on ELF, but allow the individual load
  32. segments of a binary to be located in memory independently of each
  33. other. This makes this format ideal for use in environments where no
  34. MMU is available as it still permits text segments to be shared,
  35. even if data segments are not.
  36. It is also possible to run FDPIC ELF binaries on MMU linux also.
  37. config BINFMT_FLAT
  38. bool "Kernel support for flat binaries"
  39. depends on !MMU && (!FRV || BROKEN)
  40. help
  41. Support uClinux FLAT format binaries.
  42. config BINFMT_ZFLAT
  43. bool "Enable ZFLAT support"
  44. depends on BINFMT_FLAT
  45. select ZLIB_INFLATE
  46. help
  47. Support FLAT format compressed binaries
  48. config BINFMT_SHARED_FLAT
  49. bool "Enable shared FLAT support"
  50. depends on BINFMT_FLAT
  51. help
  52. Support FLAT shared libraries
  53. config BINFMT_AOUT
  54. tristate "Kernel support for a.out and ECOFF binaries"
  55. depends on ARCH_SUPPORTS_AOUT && \
  56. (X86_32 || ALPHA || ARM || M68K)
  57. ---help---
  58. A.out (Assembler.OUTput) is a set of formats for libraries and
  59. executables used in the earliest versions of UNIX. Linux used
  60. the a.out formats QMAGIC and ZMAGIC until they were replaced
  61. with the ELF format.
  62. The conversion to ELF started in 1995. This option is primarily
  63. provided for historical interest and for the benefit of those
  64. who need to run binaries from that era.
  65. Most people should answer N here. If you think you may have
  66. occasional use for this format, enable module support above
  67. and answer M here to compile this support as a module called
  68. binfmt_aout.
  69. If any crucial components of your system (such as /sbin/init
  70. or /lib/ld.so) are still in a.out format, you will have to
  71. say Y here.
  72. config OSF4_COMPAT
  73. bool "OSF/1 v4 readv/writev compatibility"
  74. depends on ALPHA && BINFMT_AOUT
  75. help
  76. Say Y if you are using OSF/1 binaries (like Netscape and Acrobat)
  77. with v4 shared libraries freely available from Compaq. If you're
  78. going to use shared libraries from Tru64 version 5.0 or later, say N.
  79. config BINFMT_EM86
  80. tristate "Kernel support for Linux/Intel ELF binaries"
  81. depends on ALPHA
  82. ---help---
  83. Say Y here if you want to be able to execute Linux/Intel ELF
  84. binaries just like native Alpha binaries on your Alpha machine. For
  85. this to work, you need to have the emulator /usr/bin/em86 in place.
  86. You can get the same functionality by saying N here and saying Y to
  87. "Kernel support for MISC binaries".
  88. You may answer M to compile the emulation support as a module and
  89. later load the module when you want to use a Linux/Intel binary. The
  90. module will be called binfmt_em86. If unsure, say Y.
  91. config BINFMT_SOM
  92. tristate "Kernel support for SOM binaries"
  93. depends on PARISC && HPUX
  94. help
  95. SOM is a binary executable format inherited from HP/UX. Say
  96. Y here to be able to load and execute SOM binaries directly.
  97. config BINFMT_MISC
  98. tristate "Kernel support for MISC binaries"
  99. ---help---
  100. If you say Y here, it will be possible to plug wrapper-driven binary
  101. formats into the kernel. You will like this especially when you use
  102. programs that need an interpreter to run like Java, Python, .NET or
  103. Emacs-Lisp. It's also useful if you often run DOS executables under
  104. the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
  105. <http://www.tldp.org/docs.html#howto>). Once you have
  106. registered such a binary class with the kernel, you can start one of
  107. those programs simply by typing in its name at a shell prompt; Linux
  108. will automatically feed it to the correct interpreter.
  109. You can do other nice things, too. Read the file
  110. <file:Documentation/binfmt_misc.txt> to learn how to use this
  111. feature, <file:Documentation/java.txt> for information about how
  112. to include Java support. and <file:Documentation/mono.txt> for
  113. information about how to include Mono-based .NET support.
  114. To use binfmt_misc, you will need to mount it:
  115. mount binfmt_misc -t binfmt_misc /proc/sys/fs/binfmt_misc
  116. You may say M here for module support and later load the module when
  117. you have use for it; the module is called binfmt_misc. If you
  118. don't know what to answer at this point, say Y.