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