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