Lines Matching refs:to

13 	  systems. Saying Y here will enable your kernel to run ELF binaries
17 	  to run executables from different architectures or operating systems
20 	  want to say Y here.
27 	  you'll have to install the newest ELF runtime libraries, including
55 	  segments of a binary to be located in memory independently of each
57 	  MMU is available as it still permits text segments to be shared,
60 	  It is also possible to run FDPIC ELF binaries on MMU linux also.
77 	  the first page of the file in a core dump makes it possible to
79 	  cost and disk space to dump all the text.  However, versions of
93 	  Say Y here if you want to execute interpreted scripts starting with
94 	  #! followed by the path to an interpreter.
97 	  gets loaded, you cannot run scripts.  Thus, if you want to load this
153 	  The conversion to ELF started in 1995.  This option is primarily
155 	  who need to run binaries from that era.
159 	  and answer M here to compile this support as a module called
163 	  or /lib/ld.so) are still in a.out format, you will have to
172 	  going to use shared libraries from Tru64 version 5.0 or later, say N.
177 	  If you say Y here, it will be possible to plug wrapper-driven binary
179 	  programs that need an interpreter to run like Java, Python, .NET or
185 	  will automatically feed it to the correct interpreter.
188 	  <file:Documentation/admin-guide/binfmt-misc.rst> to learn how to use this
190 	  to include Java support. and <file:Documentation/admin-guide/mono.rst> for
191           information about how to include Mono-based .NET support.
193           To use binfmt_misc, you will need to mount it:
198 	  don't know what to answer at this point, say Y.
205 	  certainly want to say Y here. Not necessary on systems that never