1 .\" Copyright 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
2 .\" 2001 Free Software Foundation, Inc.
3 .\" See section COPYING for conditions for redistribution
4 .TH ld 1 "" "Free Software Foundation" "GNU Development Tools"
31 .RB "[\|" \-Bstatic "\|]"
32 .RB "[\|" \-Bdynamic "\|]"
33 .RB "[\|" \-Bsymbolic "\|]"
37 .RB "[\|" \-\-cref "\|]"
38 .RB "[\|" \-d | \-dc | \-dp\c
41 .RB "[\|" "\-defsym\ "\c
46 .RB "[\|" \-\-demangle "\|]"
47 .RB "[\|" \-\-no\-demangle "\|]"
51 .RB "[\|" \-embedded\-relocs "\|]"
53 .RB "[\|" \-export\-dynamic "\|]"
57 .RB "[\|" "\-\-auxiliary\ "\c
63 .RB "[\|" "\-\-filter\ "\c
66 .RB "[\|" "\-format\ "\c
76 .RB "[\|" "\-soname\ "\c
79 .RB "[\|" \-\-help "\|]"
94 .RB "[\|" \-n | \-N "\|]"
95 .RB "[\|" \-noinhibit-exec "\|]"
96 .RB "[\|" \-no\-keep\-memory "\|]"
97 .RB "[\|" \-no\-warn\-mismatch "\|]"
101 .RB "[\|" "\--oformat\ "\c
107 .RB "[\|" \-relax "\|]"
108 .RB "[\|" \-r | \-Ur "\|]"
109 .RB "[\|" "\-rpath\ "\c
112 .RB "[\|" "\-rpath\-link\ "\c
117 .RB "[\|" \-shared "\|]"
118 .RB "[\|" \-sort\-common "\|]"
119 .RB "[\|" "\-split\-by\-reloc\ "\c
122 .RB "[\|" \-split\-by\-file "\|]"
126 .RB "[\|" "\-\-section\-start\ "\c
131 .RB "[\|" "\-Ttext\ "\c
134 .RB "[\|" "\-Tdata\ "\c
137 .RB "[\|" "\-Tbss\ "\c
146 .RB "[\|" \-\-verbose "\|]"
147 .RB "[\|" \-\-version "\|]"
148 .RB "[\|" \-warn\-common "\|]"
149 .RB "[\|" \-warn\-constructors "\|]"
150 .RB "[\|" \-warn\-multiple\-gp "\|]"
151 .RB "[\|" \-warn\-once "\|]"
152 .RB "[\|" \-warn\-section\-align "\|]"
153 .RB "[\|" \-\-whole\-archive "\|]"
154 .RB "[\|" \-\-no\-whole\-archive "\|]"
155 .RB "[\|" "\-\-wrap\ "\c
165 \& combines a number of object and archive files, relocates
166 their data and ties up symbol references. Often the last step in
167 building a new compiled program to run is a call to \c
173 \& accepts Linker Command Language files
174 to provide explicit and total control over the linking process.
175 This man page does not describe the command language; see the `\|\c
182 \&, for full details on the command language and on other aspects of
187 \& uses the general purpose BFD libraries
188 to operate on object files. This allows \c
190 \& to read, combine, and
191 write object files in many different formats\(em\&for example, COFF or
194 \&. Different formats may be linked together to produce any
195 available kind of object file. You can use `\|\c
197 \|' to get a list of formats supported on various architectures; see
200 Aside from its flexibility, the GNU linker is more helpful than other
201 linkers in providing diagnostic information. Many linkers abandon
202 execution immediately upon encountering an error; whenever possible,
205 \& continues executing, allowing you to identify other errors
206 (or, in some cases, to get an output file in spite of the error).
210 \& is meant to cover a broad range of situations,
211 and to be as compatible as possible with other linkers. As a result,
212 you have many choices to control its behavior through the command line,
213 and through environment variables.
216 The plethora of command-line options may seem intimidating, but in
217 actual practice few of them are used in any particular context.
218 For instance, a frequent use of \c
220 \& is to link standard Unix
221 object files on a standard, supported Unix system. On such a system, to
227 $\ ld\ \-o\ output\ /lib/crt0.o\ hello.o\ \-lc
232 \& to produce a file called \c
235 result of linking the file \c
242 \& which will come from the standard search
245 The command-line options to \c
247 \& may be specified in any order, and
248 may be repeated at will. For the most part, repeating an option with a
249 different argument will either have no further effect, or override prior
250 occurrences (those further to the left on the command line) of an
253 The exceptions\(em\&which may meaningfully be used more than once\(em\&are
258 \& (or its synonym \c
263 .B \-\-section\-start\c
274 The list of object files to be linked together, shown as \c
277 may follow, precede, or be mixed in with command-line options; save that
280 \& argument may not be placed between an option flag and
283 Usually the linker is invoked with at least one object file, but other
284 forms of binary input files can also be specified with \c
289 \&, and the script command language. If \c
292 files at all are specified, the linker does not produce any output, and
293 issues the message `\|\c
297 Option arguments must either follow the option letter without intervening
298 whitespace, or be given as separate arguments immediately following the
299 option that requires them.
302 .BI "-A" "architecture"
303 In the current release of \c
305 \&, this option is useful only for the
306 Intel 960 family of architectures. In that \c
308 \& configuration, the
311 \& argument is one of the two-letter names identifying
312 members of the 960 family; the option specifies the desired output
313 target, and warns of any incompatible instructions in the input files.
314 It also modifies the linker's search strategy for archive libraries, to
315 support the use of libraries specific to each particular
316 architecture, by including in the search loop names suffixed with the
317 string identifying the architecture.
319 For example, if your \c
321 \& command line included `\|\c
326 \|', the linker would look (in its built-in search
327 paths, and in any paths you specify with \c
329 \&) for a library with
343 The first two possibilities would be considered in any event; the last
344 two are due to the use of `\|\c
348 Future releases of \c
350 \& may support similar functionality for
351 other architecture families.
353 You can meaningfully use \c
355 \& more than once on a command line, if
356 an architecture family allows combination of target architectures; each
357 use will add another pair of name variants to search for when \c
362 .BI "\-b " "input-format"
363 Specify the binary format for input object files that follow this option
364 on the command line. You don't usually need to specify this, as
367 \& is configured to expect as a default input format the most
368 usual format on each machine. \c
370 \& is a text string, the
371 name of a particular format supported by the BFD libraries.
376 \& has the same effect, as does the script command
379 You may want to use this option if you are linking files with an unusual
380 binary format. You can also use \c
382 \& to switch formats explicitly (when
383 linking object files of different formats), by including
388 \& before each group of object files in a
391 The default format is taken from the environment variable
393 \&. You can also define the input
394 format from a script, using the command \c
400 Do not link against shared libraries. This is only meaningful on
401 platforms for which shared libraries are supported.
405 Link against dynamic libraries. This is only meaningful on platforms
406 for which shared libraries are supported. This option is normally the
407 default on such platforms.
411 When creating a shared library, bind references to global symbols to
412 the definition within the shared library, if any. Normally, it is
413 possible for a program linked against a shared library to override the
414 definition within the shared library. This option is only meaningful
415 on ELF platforms which support shared libraries.
418 .BI "\-c " "commandfile"
421 \& to read link commands from the file
424 \&. These commands will completely override \c
427 default link format (rather than adding to it); \c
430 specify everything necessary to describe the target format.
433 You may also include a script of link commands directly in the command
434 line by bracketing it between `\|\c
442 Output a cross reference table. If a linker map file is being
443 generated, the cross reference table is printed to the map file.
444 Otherwise, it is printed on the standard output.
452 These three options are equivalent; multiple forms are supported for
453 compatibility with other linkers. Use any of them to make \c
455 assign space to common symbols even if a relocatable output file is
458 \&). The script command
460 .B FORCE_COMMON_ALLOCATION\c
461 \& has the same effect.
464 .BI "-defsym " "symbol" "\fR=\fP" expression
465 Create a global symbol in the output file, containing the absolute
468 \&. You may use this option as many
469 times as necessary to define multiple symbols in the command line. A
470 limited form of arithmetic is supported for the \c
473 context: you may give a hexadecimal constant or the name of an existing
478 \& to add or subtract hexadecimal
479 constants or symbols. If you need more elaborate expressions, consider
480 using the linker command language from a script.
486 These options control whether to demangle symbol names in error
487 messages and other output. When the linker is told to demangle, it
488 tries to present symbol names in a readable fashion: it strips leading
489 underscores if they are used by the object file format, and converts
490 C++ mangled symbol names into user readable names. The linker will
491 demangle by default unless the environment variable
492 .B COLLECT_NO_DEMANGLE
493 is set. These options may be used to override the default.
500 \& as the explicit symbol for beginning execution of your
501 program, rather than the default entry point. See the `\|\c
506 discussion of defaults and other ways of specifying the
510 .B \-embedded\-relocs
511 This option is only meaningful when linking MIPS embedded PIC code,
514 option to the GNU compiler and assembler. It causes the linker to
515 create a table which may be used at runtime to relocate any data which
516 was statically initialized to pointer values. See the code in
517 testsuite/ld-empic for details.
523 When creating an ELF file, add all symbols to the dynamic symbol table.
524 Normally, the dynamic symbol table contains only symbols which are used
525 by a dynamic object. This option is needed for some uses of
531 .BI "--auxiliary " "name"
532 When creating an ELF shared object, set the internal DT_AUXILIARY field
533 to the specified name. This tells the dynamic linker that the symbol
534 table of the shared object should be used as an auxiliary filter on the
535 symbol table of the shared object
541 .BI "--filter " "name"
542 When creating an ELF shared object, set the internal DT_FILTER field to
543 the specified name. This tells the dynamic linker that the symbol table
544 of the shared object should be used as a filter on the symbol table of
549 .BI "\-format " "input\-format"
558 Accepted, but ignored; provided for compatibility with other tools.
562 Set the maximum size of objects to be optimized using the GP register
565 under MIPS ECOFF. Ignored for other object file formats.
570 .BI "-soname " "name"
571 When creating an ELF shared object, set the internal DT_SONAME field to
572 the specified name. When an executable is linked with a shared object
573 which has a DT_SONAME field, then when the executable is run the dynamic
574 linker will attempt to load the shared object specified by the DT_SONAME
575 field rather than the using the file name given to the linker.
579 Print a summary of the command-line options on the standard output and exit.
582 begin with two dashes instead of one
583 for compatibility with other GNU programs. The other options start with
584 only one dash for compatibility with other linkers.
588 Perform an incremental link (same as option \c
595 Add an archive file \c
597 \& to the list of files to link. This
598 option may be used any number of times. \c
601 path-list for occurrences of \c
610 .BI "\-L" "searchdir"
611 This command adds path \c
613 \& to the list of paths that
616 \& will search for archive libraries. You may use this option
619 The default set of paths searched (without being specified with
622 \&) depends on what emulation mode \c
625 some cases also on how it was configured. The
626 paths can also be specified in a link script with the \c
632 Print (to the standard output file) a link map\(em\&diagnostic information
633 about where symbols are mapped by \c
635 \&, and information on global
636 common storage allocation.
639 .BI "\-Map " "mapfile"\c
642 a link map\(em\&diagnostic information
643 about where symbols are mapped by \c
645 \&, and information on global
646 common storage allocation.
649 .BI "\-m " "emulation"\c
652 linker. You can list the available emulations with the
656 options. This option overrides the compiled-in default, which is the
657 system for which you configured
662 specifies readable and writable \c
667 the output format supports Unix style magic numbers, the output is
672 When you use the `\|\c
674 \&\|' option, the linker does not page-align the
679 sets the text segment to be read only, and \c
686 Normally, the linker will not produce an output file if it encounters
687 errors during the link process. With this flag, you can specify that
688 you wish the output file retained even after non-fatal errors.
691 .B \-no\-keep\-memory
692 The linker normally optimizes for speed over memory usage by caching
693 the symbol tables of input files in memory. This option tells the
694 linker to instead optimize for memory usage, by rereading the symbol
695 tables as necessary. This may be required if the linker runs out of
696 memory space while linking a large executable.
699 .B \-no\-warn\-mismatch
700 Normally the linker will give an error if you try to link together
701 input files that are mismatched for some reason, perhaps because they
702 have been compiled for different processors or for different
703 endiannesses. This option tells the linker that it should silently
704 permit such possible errors. This option should only be used with
705 care, in cases when you have taken some special action that ensures
706 that the linker errors are inappropriate.
711 \& is a name for the program produced by \c
714 option is not specified, the name `\|\c
716 \|' is used by default. The
719 \& can also specify the output file name.
723 Generate optimized output files. This might use significantly more
724 time and therefore probably should be enabled only for generating the
728 \& is supposed to be a numeric value. Any value greater than zero enables
732 .BI "\--oformat " "output\-format"
733 Specify the binary format for the output object file.
734 You don't usually need to specify this, as
737 \& is configured to produce as a default output format the most
738 usual format on each machine. \c
740 \& is a text string, the
741 name of a particular format supported by the BFD libraries.
744 can also specify the output format, but this option overrides it.
747 .BI "\-R " "filename"
748 Read symbol names and their addresses from \c
751 relocate it or include it in the output. This allows your output file
752 to refer symbolically to absolute locations of memory defined in other
757 An option with machine dependent effects. Currently this option is only
758 supported on the H8/300.
760 On some platforms, use this option to perform global optimizations that
761 become possible when the linker resolves addressing in your program, such
762 as relaxing address modes and synthesizing new instructions in the
765 On platforms where this is not supported, `\|\c
767 \&\|' is accepted, but has no effect.
771 Generates relocatable output\(em\&i.e., generate an output file that can in
772 turn serve as input to \c
774 \&. This is often called \c
777 \&. As a side effect, in environments that support standard Unix
778 magic numbers, this option also sets the output file's magic number to
782 If this option is not specified, an absolute file is produced. When
783 linking C++ programs, this option \c
785 \& resolve references to
788 \& is an alternative.
790 This option does the same as \c
795 .B \-rpath\ \fIdirectory
796 Add a directory to the runtime library search path. This is used when
797 linking an ELF executable with shared objects. All
799 arguments are concatenated and passed to the runtime linker, which uses
800 them to locate shared objects at runtime. The
802 option is also used when locating shared objects which are needed by
803 shared objects explicitly included in the link; see the description of
808 is not used when linking an ELF executable, the contents of the
811 will be used if it is defined.
815 option may also be used on SunOS. By default, on SunOS, the linker
816 will form a runtime search path out of all the
818 options it is given. If a
820 option is used, the runtime search path will be formed exclusively
826 options. This can be useful when using gcc, which adds many
828 options which may be on NFS mounted filesystems.
831 .B \-rpath\-link\ \fIdirectory
832 When using ELF or SunOS, one shared library may require another. This
835 link includes a shared library as one of the input files.
837 When the linker encounters such a dependency when doing a non-shared,
838 non-relocateable link, it will automatically try to locate the required
839 shared library and include it in the link, if it is not included
840 explicitly. In such a case, the
842 option specifies the first set of directories to search. The
844 option may specify a sequence of directory names either by specifying
845 a list of names separated by colons, or by appearing multiple times.
847 If the required shared library is not found, the linker will issue a
848 warning and continue with the link.
852 Omits debugger symbol information (but not all symbols) from the output file.
856 Omits all symbol information from the output file.
860 Create a shared library. This is currently only supported on ELF and
861 SunOS platforms (on SunOS it is not required, as the linker will
862 automatically create a shared library when there are undefined symbols
871 places the global common symbols in the appropriate output sections,
872 it sorts them by size. First come all the one byte symbols, then all
873 the two bytes, then all the four bytes, and then everything else.
874 This is to prevent gaps between symbols due to
875 alignment constraints. This option disables that sorting.
878 .B \-split\-by\-reloc\ \fIcount
879 Trys to creates extra sections in the output file so that no single
880 output section in the file contains more than
883 This is useful when generating huge relocatable for downloading into
884 certain real time kernels with the COFF object file format; since COFF
885 cannot represent more than 65535 relocations in a single section.
886 Note that this will fail to work with object file formats which do not
887 support arbitrary sections. The linker will not split up individual
888 input sections for redistribution, so if a single input section
891 relocations one output section will contain that many relocations.
896 .B \-split\-by\-reloc
897 but creates a new output section for each input file.
900 .BI "--section-start " "sectionname" "\fR=\fP"org
901 Locate a section in the output file at the absolute
907 \& must be a hexadecimal integer.
908 You may use this option as many
909 times as necessary to locate multiple sections in the command
910 line. If you need more elaborate expressions, consider
911 using the linker command language from a script.
914 .BI "\-Tbss " "org"\c
916 .BI "\-Tdata " "org"\c
918 .BI "\-Ttext " "org"\c
921 \& as the starting address for\(em\&respectively\(em\&the
928 \& segment of the output file.
931 \& must be a hexadecimal integer.
934 .BI "\-T " "commandfile"
939 \&; supported for compatibility with
944 Prints names of input files as \c
952 \& to be entered in the output file as an undefined symbol.
953 This may, for example, trigger linking of additional modules from
954 standard libraries. \c
956 \& may be repeated with different option
957 arguments to enter additional undefined symbols.
961 For anything other than C++ programs, this option is equivalent to
964 \&: it generates relocatable output\(em\&i.e., an output file that can in
965 turn serve as input to \c
967 \&. When linking C++ programs, \c
970 \& resolve references to constructors, unlike \c
976 Display the version number for \c
978 and list the supported emulations.
979 Display which input files can and can not be opened.
983 Display the version number for \c
988 option also lists the supported emulations.
992 Display the version number for \c
998 Warn when a common symbol is combined with another common symbol or with
999 a symbol definition. Unix linkers allow this somewhat sloppy practice,
1000 but linkers on some other operating systems do not. This option allows
1001 you to find potential problems from combining global symbols.
1004 .B \-warn\-constructors
1005 Warn if any global constructors are used. This is only useful for a
1006 few object file formats. For formats like COFF or ELF, the linker can
1007 not detect the use of global constructors.
1010 .B \-warn\-multiple\-gp
1011 Warn if the output file requires multiple global-pointer values. This
1012 option is only meaningful for certain processors, such as the Alpha.
1016 Only warn once for each undefined symbol, rather than once per module
1020 .B \-warn\-section\-align
1021 Warn if the address of an output section is changed because of
1022 alignment. Typically, the alignment will be set by an input section.
1023 The address will only be changed if it not explicitly specified; that
1024 is, if the SECTIONS command does not specify a start address for the
1028 .B \-\-whole\-archive
1029 For each archive mentioned on the command line after the
1030 .B \-\-whole\-archive
1031 option, include every object file in the archive in the link, rather
1032 than searching the archive for the required object files. This is
1033 normally used to turn an archive file into a shared library, forcing
1034 every object to be included in the resulting shared library.
1037 .B \-\-no\-whole\-archive
1038 Turn off the effect of the
1039 .B \-\-whole\-archive
1040 option for archives which appear later on the command line.
1043 .BI "--wrap " "symbol"
1044 Use a wrapper function for
1046 Any undefined reference to
1049 .BI "__wrap_" "symbol".
1050 Any undefined reference to
1051 .BI "__real_" "symbol"
1057 Delete all temporary local symbols. For most targets, this is all local
1058 symbols whose names begin with `\|\c
1064 Delete all local symbols.
1070 You can change the behavior of
1072 \& with the environment variable \c
1078 \& determines the input-file object format if you don't
1081 \& (or its synonym \c
1083 \&). Its value should be one
1084 of the BFD names for an input format. If there is no
1087 \& in the environment, \c
1089 \& uses the natural format
1094 \& then BFD attempts to discover the
1095 input format by examining binary input files; this method often
1096 succeeds, but there are potential ambiguities, since there is no method
1097 of ensuring that the magic number used to flag object-file formats is
1098 unique. However, the configuration procedure for BFD on each system
1099 places the conventional format for that system first in the search-list,
1100 so ambiguities are resolved in favor of convention.
1109 .RB "`\|" ld "\|' and `\|" binutils "\|'"
1114 ld: the GNU linker\c
1115 , Steve Chamberlain and Roland Pesch;
1117 The GNU Binary Utilities\c
1121 Copyright (c) 1991, 92, 93, 94, 95, 96, 97, 1998, 2000 Free Software Foundation, Inc.
1123 This document is distributed under the terms of the GNU Free
1124 Documentation License, version 1.1. That license is described in the
1125 sources for this manual page, but it is not displayed here in order to
1126 make this manual more consise. Copies of this license can also be
1127 obtained from: http://www.gnu.org/copyleft/.
1129 \" .SH GNU Free Documentation License
1130 \" Version 1.1, March 2000
1132 \" Copyright (C) 2000 Free Software Foundation, Inc.
1133 \" 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
1135 \" Everyone is permitted to copy and distribute verbatim
1136 \" copies of this license document, but changing it is
1141 \" The purpose of this License is to make a manual, textbook, or other
1142 \" written document "free" in the sense of freedom: to assure everyone
1143 \" the effective freedom to copy and redistribute it, with or without
1144 \" modifying it, either commercially or noncommercially. Secondarily,
1145 \" this License preserves for the author and publisher a way to get
1146 \" credit for their work, while not being considered responsible for
1147 \" modifications made by others.
1149 \" This License is a kind of "copyleft", which means that derivative
1150 \" works of the document must themselves be free in the same sense. It
1151 \" complements the GNU General Public License, which is a copyleft
1152 \" license designed for free software.
1154 \" We have designed this License in order to use it for manuals for free
1155 \" software, because free software needs free documentation: a free
1156 \" program should come with manuals providing the same freedoms that the
1157 \" software does. But this License is not limited to software manuals;
1158 \" it can be used for any textual work, regardless of subject matter or
1159 \" whether it is published as a printed book. We recommend this License
1160 \" principally for works whose purpose is instruction or reference.
1162 \" 1. APPLICABILITY AND DEFINITIONS
1164 \" This License applies to any manual or other work that contains a
1165 \" notice placed by the copyright holder saying it can be distributed
1166 \" under the terms of this License. The "Document", below, refers to any
1167 \" such manual or work. Any member of the public is a licensee, and is
1168 \" addressed as "you".
1170 \" A "Modified Version" of the Document means any work containing the
1171 \" Document or a portion of it, either copied verbatim, or with
1172 \" modifications and/or translated into another language.
1174 \" A "Secondary Section" is a named appendix or a front-matter section of
1175 \" the Document that deals exclusively with the relationship of the
1176 \" publishers or authors of the Document to the Document's overall subject
1177 \" (or to related matters) and contains nothing that could fall directly
1178 \" within that overall subject. (For example, if the Document is in part a
1179 \" textbook of mathematics, a Secondary Section may not explain any
1180 \" mathematics.) The relationship could be a matter of historical
1181 \" connection with the subject or with related matters, or of legal,
1182 \" commercial, philosophical, ethical or political position regarding
1185 \" The "Invariant Sections" are certain Secondary Sections whose titles
1186 \" are designated, as being those of Invariant Sections, in the notice
1187 \" that says that the Document is released under this License.
1189 \" The "Cover Texts" are certain short passages of text that are listed,
1190 \" as Front-Cover Texts or Back-Cover Texts, in the notice that says that
1191 \" the Document is released under this License.
1193 \" A "Transparent" copy of the Document means a machine-readable copy,
1194 \" represented in a format whose specification is available to the
1195 \" general public, whose contents can be viewed and edited directly and
1196 \" straightforwardly with generic text editors or (for images composed of
1197 \" pixels) generic paint programs or (for drawings) some widely available
1198 \" drawing editor, and that is suitable for input to text formatters or
1199 \" for automatic translation to a variety of formats suitable for input
1200 \" to text formatters. A copy made in an otherwise Transparent file
1201 \" format whose markup has been designed to thwart or discourage
1202 \" subsequent modification by readers is not Transparent. A copy that is
1203 \" not "Transparent" is called "Opaque".
1205 \" Examples of suitable formats for Transparent copies include plain
1206 \" ASCII without markup, Texinfo input format, LaTeX input format, SGML
1207 \" or XML using a publicly available DTD, and standard-conforming simple
1208 \" HTML designed for human modification. Opaque formats include
1209 \" PostScript, PDF, proprietary formats that can be read and edited only
1210 \" by proprietary word processors, SGML or XML for which the DTD and/or
1211 \" processing tools are not generally available, and the
1212 \" machine-generated HTML produced by some word processors for output
1215 \" The "Title Page" means, for a printed book, the title page itself,
1216 \" plus such following pages as are needed to hold, legibly, the material
1217 \" this License requires to appear in the title page. For works in
1218 \" formats which do not have any title page as such, "Title Page" means
1219 \" the text near the most prominent appearance of the work's title,
1220 \" preceding the beginning of the body of the text.
1222 \" 2. VERBATIM COPYING
1224 \" You may copy and distribute the Document in any medium, either
1225 \" commercially or noncommercially, provided that this License, the
1226 \" copyright notices, and the license notice saying this License applies
1227 \" to the Document are reproduced in all copies, and that you add no other
1228 \" conditions whatsoever to those of this License. You may not use
1229 \" technical measures to obstruct or control the reading or further
1230 \" copying of the copies you make or distribute. However, you may accept
1231 \" compensation in exchange for copies. If you distribute a large enough
1232 \" number of copies you must also follow the conditions in section 3.
1234 \" You may also lend copies, under the same conditions stated above, and
1235 \" you may publicly display copies.
1237 \" 3. COPYING IN QUANTITY
1239 \" If you publish printed copies of the Document numbering more than 100,
1240 \" and the Document's license notice requires Cover Texts, you must enclose
1241 \" the copies in covers that carry, clearly and legibly, all these Cover
1242 \" Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
1243 \" the back cover. Both covers must also clearly and legibly identify
1244 \" you as the publisher of these copies. The front cover must present
1245 \" the full title with all words of the title equally prominent and
1246 \" visible. You may add other material on the covers in addition.
1247 \" Copying with changes limited to the covers, as long as they preserve
1248 \" the title of the Document and satisfy these conditions, can be treated
1249 \" as verbatim copying in other respects.
1251 \" If the required texts for either cover are too voluminous to fit
1252 \" legibly, you should put the first ones listed (as many as fit
1253 \" reasonably) on the actual cover, and continue the rest onto adjacent
1256 \" If you publish or distribute Opaque copies of the Document numbering
1257 \" more than 100, you must either include a machine-readable Transparent
1258 \" copy along with each Opaque copy, or state in or with each Opaque copy
1259 \" a publicly-accessible computer-network location containing a complete
1260 \" Transparent copy of the Document, free of added material, which the
1261 \" general network-using public has access to download anonymously at no
1262 \" charge using public-standard network protocols. If you use the latter
1263 \" option, you must take reasonably prudent steps, when you begin
1264 \" distribution of Opaque copies in quantity, to ensure that this
1265 \" Transparent copy will remain thus accessible at the stated location
1266 \" until at least one year after the last time you distribute an Opaque
1267 \" copy (directly or through your agents or retailers) of that edition to
1270 \" It is requested, but not required, that you contact the authors of the
1271 \" Document well before redistributing any large number of copies, to give
1272 \" them a chance to provide you with an updated version of the Document.
1276 \" You may copy and distribute a Modified Version of the Document under
1277 \" the conditions of sections 2 and 3 above, provided that you release
1278 \" the Modified Version under precisely this License, with the Modified
1279 \" Version filling the role of the Document, thus licensing distribution
1280 \" and modification of the Modified Version to whoever possesses a copy
1281 \" of it. In addition, you must do these things in the Modified Version:
1283 \" A. Use in the Title Page (and on the covers, if any) a title distinct
1284 \" from that of the Document, and from those of previous versions
1285 \" (which should, if there were any, be listed in the History section
1286 \" of the Document). You may use the same title as a previous version
1287 \" if the original publisher of that version gives permission.
1289 \" B. List on the Title Page, as authors, one or more persons or entities
1290 \" responsible for authorship of the modifications in the Modified
1291 \" Version, together with at least five of the principal authors of the
1292 \" Document (all of its principal authors, if it has less than five).
1294 \" C. State on the Title page the name of the publisher of the
1295 \" Modified Version, as the publisher.
1297 \" D. Preserve all the copyright notices of the Document.
1299 \" E. Add an appropriate copyright notice for your modifications
1300 \" adjacent to the other copyright notices.
1302 \" F. Include, immediately after the copyright notices, a license notice
1303 \" giving the public permission to use the Modified Version under the
1304 \" terms of this License, in the form shown in the Addendum below.
1305 \" Preserve in that license notice the full lists of Invariant Sections
1306 \" and required Cover Texts given in the Document's license notice.
1308 \" H. Include an unaltered copy of this License.
1310 \" I. Preserve the section entitled "History", and its title, and add to
1311 \" it an item stating at least the title, year, new authors, and
1312 \" publisher of the Modified Version as given on the Title Page. If
1313 \" there is no section entitled "History" in the Document, create one
1314 \" stating the title, year, authors, and publisher of the Document as
1315 \" given on its Title Page, then add an item describing the Modified
1316 \" Version as stated in the previous sentence.
1318 \" J. Preserve the network location, if any, given in the Document for
1319 \" public access to a Transparent copy of the Document, and likewise
1320 \" the network locations given in the Document for previous versions
1321 \" it was based on. These may be placed in the "History" section.
1322 \" You may omit a network location for a work that was published at
1323 \" least four years before the Document itself, or if the original
1324 \" publisher of the version it refers to gives permission.
1326 \" K. In any section entitled "Acknowledgements" or "Dedications",
1327 \" preserve the section's title, and preserve in the section all the
1328 \" substance and tone of each of the contributor acknowledgements
1329 \" and/or dedications given therein.
1331 \" L. Preserve all the Invariant Sections of the Document,
1332 \" unaltered in their text and in their titles. Section numbers
1333 \" or the equivalent are not considered part of the section titles.
1335 \" M. Delete any section entitled "Endorsements". Such a section
1336 \" may not be included in the Modified Version.
1338 \" N. Do not retitle any existing section as "Endorsements"
1339 \" or to conflict in title with any Invariant Section.
1341 \" If the Modified Version includes new front-matter sections or
1342 \" appendices that qualify as Secondary Sections and contain no material
1343 \" copied from the Document, you may at your option designate some or all
1344 \" of these sections as invariant. To do this, add their titles to the
1345 \" list of Invariant Sections in the Modified Version's license notice.
1346 \" These titles must be distinct from any other section titles.
1348 \" You may add a section entitled "Endorsements", provided it contains
1349 \" nothing but endorsements of your Modified Version by various
1350 \" parties--for example, statements of peer review or that the text has
1351 \" been approved by an organization as the authoritative definition of a
1354 \" You may add a passage of up to five words as a Front-Cover Text, and a
1355 \" passage of up to 25 words as a Back-Cover Text, to the end of the list
1356 \" of Cover Texts in the Modified Version. Only one passage of
1357 \" Front-Cover Text and one of Back-Cover Text may be added by (or
1358 \" through arrangements made by) any one entity. If the Document already
1359 \" includes a cover text for the same cover, previously added by you or
1360 \" by arrangement made by the same entity you are acting on behalf of,
1361 \" you may not add another; but you may replace the old one, on explicit
1362 \" permission from the previous publisher that added the old one.
1364 \" The author(s) and publisher(s) of the Document do not by this License
1365 \" give permission to use their names for publicity for or to assert or
1366 \" imply endorsement of any Modified Version.
1369 \" 5. COMBINING DOCUMENTS
1371 \" You may combine the Document with other documents released under this
1372 \" License, under the terms defined in section 4 above for modified
1373 \" versions, provided that you include in the combination all of the
1374 \" Invariant Sections of all of the original documents, unmodified, and
1375 \" list them all as Invariant Sections of your combined work in its
1378 \" The combined work need only contain one copy of this License, and
1379 \" multiple identical Invariant Sections may be replaced with a single
1380 \" copy. If there are multiple Invariant Sections with the same name but
1381 \" different contents, make the title of each such section unique by
1382 \" adding at the end of it, in parentheses, the name of the original
1383 \" author or publisher of that section if known, or else a unique number.
1384 \" Make the same adjustment to the section titles in the list of
1385 \" Invariant Sections in the license notice of the combined work.
1387 \" In the combination, you must combine any sections entitled "History"
1388 \" in the various original documents, forming one section entitled
1389 \" "History"; likewise combine any sections entitled "Acknowledgements",
1390 \" and any sections entitled "Dedications". You must delete all sections
1391 \" entitled "Endorsements."
1394 \" 6. COLLECTIONS OF DOCUMENTS
1396 \" You may make a collection consisting of the Document and other documents
1397 \" released under this License, and replace the individual copies of this
1398 \" License in the various documents with a single copy that is included in
1399 \" the collection, provided that you follow the rules of this License for
1400 \" verbatim copying of each of the documents in all other respects.
1402 \" You may extract a single document from such a collection, and distribute
1403 \" it individually under this License, provided you insert a copy of this
1404 \" License into the extracted document, and follow this License in all
1405 \" other respects regarding verbatim copying of that document.
1408 \" 7. AGGREGATION WITH INDEPENDENT WORKS
1410 \" A compilation of the Document or its derivatives with other separate
1411 \" and independent documents or works, in or on a volume of a storage or
1412 \" distribution medium, does not as a whole count as a Modified Version
1413 \" of the Document, provided no compilation copyright is claimed for the
1414 \" compilation. Such a compilation is called an "aggregate", and this
1415 \" License does not apply to the other self-contained works thus compiled
1416 \" with the Document, on account of their being thus compiled, if they
1417 \" are not themselves derivative works of the Document.
1419 \" If the Cover Text requirement of section 3 is applicable to these
1420 \" copies of the Document, then if the Document is less than one quarter
1421 \" of the entire aggregate, the Document's Cover Texts may be placed on
1422 \" covers that surround only the Document within the aggregate.
1423 \" Otherwise they must appear on covers around the whole aggregate.
1428 \" Translation is considered a kind of modification, so you may
1429 \" distribute translations of the Document under the terms of section 4.
1430 \" Replacing Invariant Sections with translations requires special
1431 \" permission from their copyright holders, but you may include
1432 \" translations of some or all Invariant Sections in addition to the
1433 \" original versions of these Invariant Sections. You may include a
1434 \" translation of this License provided that you also include the
1435 \" original English version of this License. In case of a disagreement
1436 \" between the translation and the original English version of this
1437 \" License, the original English version will prevail.
1442 \" You may not copy, modify, sublicense, or distribute the Document except
1443 \" as expressly provided for under this License. Any other attempt to
1444 \" copy, modify, sublicense or distribute the Document is void, and will
1445 \" automatically terminate your rights under this License. However,
1446 \" parties who have received copies, or rights, from you under this
1447 \" License will not have their licenses terminated so long as such
1448 \" parties remain in full compliance.
1451 \" 10. FUTURE REVISIONS OF THIS LICENSE
1453 \" The Free Software Foundation may publish new, revised versions
1454 \" of the GNU Free Documentation License from time to time. Such new
1455 \" versions will be similar in spirit to the present version, but may
1456 \" differ in detail to address new problems or concerns. See
1457 \" http://www.gnu.org/copyleft/.
1459 \" Each version of the License is given a distinguishing version number.
1460 \" If the Document specifies that a particular numbered version of this
1461 \" License "or any later version" applies to it, you have the option of
1462 \" following the terms and conditions either of that specified version or
1463 \" of any later version that has been published (not as a draft) by the
1464 \" Free Software Foundation. If the Document does not specify a version
1465 \" number of this License, you may choose any version ever published (not
1466 \" as a draft) by the Free Software Foundation.
1469 \" ADDENDUM: How to use this License for your documents
1471 \" To use this License in a document you have written, include a copy of
1472 \" the License in the document and put the following copyright and
1473 \" license notices just after the title page:
1475 \" Copyright (c) YEAR YOUR NAME.
1476 \" Permission is granted to copy, distribute and/or
1477 \" modify this document under the terms of the GNU
1478 \" Free Documentation License, Version 1.1 or any later
1479 \" version published by the Free Software Foundation;
1480 \" with the Invariant Sections being LIST THEIR TITLES,
1481 \" with the Front-Cover Texts being LIST, and with the
1482 \" Back-Cover Texts being LIST. A copy of the license
1483 \" is included in the section entitled "GNU Free
1484 \" Documentation License".
1486 \" If you have no Invariant Sections, write "with no Invariant Sections"
1487 \" instead of saying which ones are invariant. If you have no
1488 \" Front-Cover Texts, write "no Front-Cover Texts" instead of
1489 \" "Front-Cover Texts being LIST"; likewise for Back-Cover Texts.
1491 \" If your document contains nontrivial examples of program code, we
1492 \" recommend releasing these examples in parallel under your choice of
1493 \" free software license, such as the GNU General Public License,
1494 \" to permit their use in free software.