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