1config 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.
  17          Information about ELF is contained in the ELF HOWTO available from
  18          <>.
  20          If you find that after upgrading from Linux kernel 1.2 and saying Y
  21          here, you still can't run any ELF binaries (they just crash), then
  22          you'll have to install the newest ELF runtime libraries, including
  23 (check the file <file:Documentation/Changes> for location and
  24          latest version).
  27        bool
  28        depends on COMPAT && BINFMT_ELF
  31        bool "Kernel support for FDPIC ELF binaries"
  32        default y
  33        depends on (FRV || BLACKFIN || (SUPERH32 && !MMU))
  34        help
  35          ELF FDPIC binaries are based on ELF, but allow the individual load
  36          segments of a binary to be located in memory independently of each
  37          other. This makes this format ideal for use in environments where no
  38          MMU is available as it still permits text segments to be shared,
  39          even if data segments are not.
  41          It is also possible to run FDPIC ELF binaries on MMU linux also.
  44        bool "Write ELF core dumps with partial segments"
  45        default n
  46        depends on BINFMT_ELF && ELF_CORE
  47        help
  48          ELF core dump files describe each memory mapping of the crashed
  49          process, and can contain or omit the memory contents of each one.
  50          The contents of an unmodified text mapping are omitted by default.
  52          For an unmodified text mapping of an ELF object, including just
  53          the first page of the file in a core dump makes it possible to
  54          identify the build ID bits in the file, without paying the i/o
  55          cost and disk space to dump all the text.  However, versions of
  56          GDB before 6.7 are confused by ELF core dump files in this format.
  58          The core dump behavior can be controlled per process using
  59          the /proc/PID/coredump_filter pseudo-file; this setting is
  60          inherited.  See Documentation/filesystems/proc.txt for details.
  62          This config option changes the default setting of coredump_filter
  63          seen at boot time.  If unsure, say N.
  65config BINFMT_FLAT
  66        bool "Kernel support for flat binaries"
  67        depends on !MMU && (!FRV || BROKEN)
  68        help
  69          Support uClinux FLAT format binaries.
  71config BINFMT_ZFLAT
  72        bool "Enable ZFLAT support"
  73        depends on BINFMT_FLAT
  74        select ZLIB_INFLATE
  75        help
  76          Support FLAT format compressed binaries
  79        bool "Enable shared FLAT support"
  80        depends on BINFMT_FLAT
  81        help
  82          Support FLAT shared libraries
  84config HAVE_AOUT
  85       def_bool n
  87config BINFMT_AOUT
  88        tristate "Kernel support for a.out and ECOFF binaries"
  89        depends on HAVE_AOUT
  90        ---help---
  91          A.out (Assembler.OUTput) is a set of formats for libraries and
  92          executables used in the earliest versions of UNIX.  Linux used
  93          the a.out formats QMAGIC and ZMAGIC until they were replaced
  94          with the ELF format.
  96          The conversion to ELF started in 1995.  This option is primarily
  97          provided for historical interest and for the benefit of those
  98          who need to run binaries from that era.
 100          Most people should answer N here.  If you think you may have
 101          occasional use for this format, enable module support above
 102          and answer M here to compile this support as a module called
 103          binfmt_aout.
 105          If any crucial components of your system (such as /sbin/init
 106          or /lib/ are still in a.out format, you will have to
 107          say Y here.
 109config OSF4_COMPAT
 110        bool "OSF/1 v4 readv/writev compatibility"
 111        depends on ALPHA && BINFMT_AOUT
 112        help
 113          Say Y if you are using OSF/1 binaries (like Netscape and Acrobat)
 114          with v4 shared libraries freely available from Compaq. If you're
 115          going to use shared libraries from Tru64 version 5.0 or later, say N.
 117config BINFMT_EM86
 118        tristate "Kernel support for Linux/Intel ELF binaries"
 119        depends on ALPHA
 120        ---help---
 121          Say Y here if you want to be able to execute Linux/Intel ELF
 122          binaries just like native Alpha binaries on your Alpha machine. For
 123          this to work, you need to have the emulator /usr/bin/em86 in place.
 125          You can get the same functionality by saying N here and saying Y to
 126          "Kernel support for MISC binaries".
 128          You may answer M to compile the emulation support as a module and
 129          later load the module when you want to use a Linux/Intel binary. The
 130          module will be called binfmt_em86. If unsure, say Y.
 132config BINFMT_SOM
 133        tristate "Kernel support for SOM binaries"
 134        depends on PARISC && HPUX
 135        help
 136          SOM is a binary executable format inherited from HP/UX.  Say
 137          Y here to be able to load and execute SOM binaries directly.
 139config BINFMT_MISC
 140        tristate "Kernel support for MISC binaries"
 141        ---help---
 142          If you say Y here, it will be possible to plug wrapper-driven binary
 143          formats into the kernel. You will like this especially when you use
 144          programs that need an interpreter to run like Java, Python, .NET or
 145          Emacs-Lisp. It's also useful if you often run DOS executables under
 146          the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
 147          <>). Once you have
 148          registered such a binary class with the kernel, you can start one of
 149          those programs simply by typing in its name at a shell prompt; Linux
 150          will automatically feed it to the correct interpreter.
 152          You can do other nice things, too. Read the file
 153          <file:Documentation/binfmt_misc.txt> to learn how to use this
 154          feature, <file:Documentation/java.txt> for information about how
 155          to include Java support. and <file:Documentation/mono.txt> for
 156          information about how to include Mono-based .NET support.
 158          To use binfmt_misc, you will need to mount it:
 159                mount binfmt_misc -t binfmt_misc /proc/sys/fs/binfmt_misc
 161          You may say M here for module support and later load the module when
 162          you have use for it; the module is called binfmt_misc. If you
 163          don't know what to answer at this point, say Y.