diff options
| -rw-r--r-- | bfd/doc/ChangeLog | 141 | ||||
| -rw-r--r-- | bfd/doc/bfd.texinfo | 389 | ||||
| -rw-r--r-- | bfd/doc/fdl.texi | 366 |
3 files changed, 454 insertions, 442 deletions
diff --git a/bfd/doc/ChangeLog b/bfd/doc/ChangeLog index 2af10b0..b133991 100644 --- a/bfd/doc/ChangeLog +++ b/bfd/doc/ChangeLog @@ -1,3 +1,10 @@ +2003-02-12 Bob Wilson <bob.wilson@acm.org> + + * bfd.texinfo: Fix quotes for texinfo. Make section title + capitalization more consistent. Use @example instead of @lisp. + Replace FDL appendix with include of fdl.texi. + * fdl.texi: New file. + 2002-11-18 Klee Dienes <kdienes@apple.com> * Makefile.am (DOCFILES): Add bfdwin.texi, bfdio.texi. @@ -172,43 +179,43 @@ Wed May 24 12:03:25 2000 Hans-Peter Nilsson <hp@axis.com> * bfdint.texi (BFD_JUMP_TABLE macros): Fix typo. -Fri Apr 7 17:54:38 2000 Andrew Cagney <cagney@b1.cygnus.com> +2000-04-07 Andrew Cagney <cagney@b1.cygnus.com> * Makefile.in: Rebuild with current autoconf/automake. -Thu Feb 4 23:21:36 1999 Ian Lance Taylor <ian@cygnus.com> +1999-02-04 Ian Lance Taylor <ian@cygnus.com> * Makefile.in: Rebuild with current autoconf/automake. -Thu Jul 23 09:36:44 1998 Nick Clifton <nickc@cygnus.com> +1998-07-23 Nick Clifton <nickc@cygnus.com> * bfdint.texi (BFD ELF processor required): Add paragraph describing the necessity to create "include/elf/CPU.h". -Thu May 7 14:45:43 1998 Ian Lance Taylor <ian@cygnus.com> +1998-05-07 Ian Lance Taylor <ian@cygnus.com> * Makefile.am (chew.o): Add -I options for intl srcdir and objdir. * Makefile.in: Rebuild. -Mon Apr 27 20:19:24 1998 Ian Lance Taylor <ian@cygnus.com> +1998-04-27 Ian Lance Taylor <ian@cygnus.com> * bfdint.texi: New file. * Makefile.am (noinst_TEXINFOS): New variable. * Makefile.in: Rebuild. -Mon Apr 13 16:48:56 1998 Ian Lance Taylor <ian@cygnus.com> +1998-04-13 Ian Lance Taylor <ian@cygnus.com> * Makefile.in: Rebuild. -Mon Apr 6 14:06:55 1998 Ian Lance Taylor <ian@cygnus.com> +1998-04-06 Ian Lance Taylor <ian@cygnus.com> * Makefile.am (STAGESTUFF): Remove variable. (CLEANFILES): Don't remove $(STAGESTUFF). (DISTCLEANFILES, MAINTAINERCLEANFILES): New variables. * Makefile.in: Rebuild. -Fri Mar 27 16:25:25 1998 Ian Lance Taylor <ian@cygnus.com> +1998-03-27 Ian Lance Taylor <ian@cygnus.com> * chew.c (skip_white_and_starts): Remove unused declaration. (skip_white_and_stars): Add casts to avoid warnings. @@ -223,12 +230,12 @@ Fri Mar 27 16:25:25 1998 Ian Lance Taylor <ian@cygnus.com> (print): Change printf format string. (main): Call usage for an unrecognized option. -Fri Feb 13 14:37:14 1998 Ian Lance Taylor <ian@cygnus.com> +1998-02-13 Ian Lance Taylor <ian@cygnus.com> * Makefile.am (AUTOMAKE_OPTIONS): Define. * Makefile.in: Rebuild. -Mon Jan 26 15:38:36 1998 Andreas Schwab <schwab@issan.informatik.uni-dortmund.de> +1998-01-26 Andreas Schwab <schwab@issan.informatik.uni-dortmund.de> * doc.str (bodytext): Don't output @* at the end. * chew.c (kill_bogus_lines): Make sure that a period at the @@ -238,45 +245,45 @@ Mon Jan 26 15:38:36 1998 Andreas Schwab <schwab@issan.informatik.uni-dortmund. * Makefile.am (s-reloc, s-syms): Depend on doc.str. * Makefile.in: Rebuild. -Wed Oct 1 14:41:28 1997 Ian Lance Taylor <ian@cygnus.com> +1997-10-01 Ian Lance Taylor <ian@cygnus.com> * Makefile.am (libbfd.h): Don't use cpu-h8300.c, cpu-i960.c, or elfcode.h as input files; they don't contribute anything. * Makefile.in: Rebuild. -Fri Aug 15 04:55:15 1997 Doug Evans <dje@canuck.cygnus.com> +1997-08-15 Doug Evans <dje@canuck.cygnus.com> * Makefile.am (libbfd.h, libcoff.h): Invoke $(MKDOC) as ./$(MKDOC). * Makefile.in: Rebuild. -Fri Aug 1 12:59:58 1997 Ian Lance Taylor <ian@cygnus.com> +1997-08-01 Ian Lance Taylor <ian@cygnus.com> * Makefile.am (CC_FOR_BUILD): Don't set explicitly. * Makefile.in: Rebuild. -Thu Jul 31 20:00:12 1997 Ian Lance Taylor <ian@cygnus.com> +1997-07-31 Ian Lance Taylor <ian@cygnus.com> * Makefile.am: New file, based on old Makefile.in. * Makefile.in: Now built with automake. -Tue Jul 22 14:44:00 1997 Robert Hoehne <robert.hoehne@Mathematik.TU-Chemnitz.DE> +1997-07-22 Robert Hoehne <robert.hoehne@Mathematik.TU-Chemnitz.DE> * Makefile.in: Change stamp-* files to s-* files. Use bfdt.texi rather than bfd.texi. (DOCFILES): Change bfd.texi to bfdt.texi. * bfd.texinfo: Include bfdt.texi, not bfd.texi. -Mon Jun 16 15:33:15 1997 Ian Lance Taylor <ian@cygnus.com> +1997-06-16 Ian Lance Taylor <ian@cygnus.com> * Makefile.in (CC, CFLAGS): Substitute from configure script. From Jeff Makey <jeff@cts.com>. -Tue Apr 15 12:37:41 1997 Ian Lance Taylor <ian@cygnus.com> +1997-04-15 Ian Lance Taylor <ian@cygnus.com> * Makefile.in (install-info): Use mkinstalldirs to build $(infodir). -Tue Apr 8 12:49:46 1997 Ian Lance Taylor <ian@cygnus.com> +1997-04-08 Ian Lance Taylor <ian@cygnus.com> * Makefile.in (install-info): Permit info files to be in srcdir. (stamp-*): Add a stamp-X target for each X.texi target. @@ -285,61 +292,61 @@ Tue Apr 8 12:49:46 1997 Ian Lance Taylor <ian@cygnus.com> (distclean): Depend upon mostlyclean. Remove stamp-*. Don't remove $(DOCFILES). -Mon Apr 7 15:23:26 1997 Ian Lance Taylor <ian@cygnus.com> +1997-04-07 Ian Lance Taylor <ian@cygnus.com> * Makefile.in (distclean): Don't remove *.info files. -Thu Feb 13 20:50:02 1997 Klaus Kaempf (kkaempf@progis.de) +1997-02-13 Klaus Kaempf (kkaempf@progis.de) * makefile.vms: New file. -Tue Jun 18 18:32:28 1996 Ian Lance Taylor <ian@cygnus.com> +1996-06-18 Ian Lance Taylor <ian@cygnus.com> * chew.c (kill_bogus_lines): Reset sl when not at the start of a line. From Uwe Ohse <uwe@tirka.gun.de>. -Tue Jan 30 14:10:46 1996 Ian Lance Taylor <ian@cygnus.com> +1996-01-30 Ian Lance Taylor <ian@cygnus.com> From Ronald F. Guilmette <rfg@monkeys.com>: * Makefile.in (libbfd.h): Depend upon proto.str. (libcoff.h, bfd.h): Likewise. -Fri Nov 3 14:46:48 1995 Fred Fish <fnf@cygnus.com> +1995-11-03 Fred Fish <fnf@cygnus.com> * Makefile.in (SRCDOC, SRCPROT, core.texi, bfd.h): Use corefile.c, renamed from core.c. -Wed Nov 1 14:28:23 1995 Manfred Hollstein KS/EF4A 60/1F/110 #40283 <manfred@lts.sel.alcatel.de> +1995-11-01 Manfred Hollstein KS/EF4A 60/1F/110 #40283 <manfred@lts.sel.alcatel.de> * chew.c: Include <ctype.h>. -Fri Oct 6 16:23:34 1995 Ken Raeburn <raeburn@cygnus.com> +1995-10-06 Ken Raeburn <raeburn@cygnus.com> Mon Sep 25 22:49:32 1995 Andreas Schwab <schwab@issan.informatik.uni-dortmund.de> * Makefile.in (Makefile): Only remake this Makefile. -Wed Oct 4 15:51:05 1995 Ken Raeburn <raeburn@cygnus.com> +1995-10-04 Ken Raeburn <raeburn@cygnus.com> * chew.c: Include <stdio.h>. -Tue Sep 12 18:14:50 1995 Ian Lance Taylor <ian@cygnus.com> +1995-09-12 Ian Lance Taylor <ian@cygnus.com> * Makefile.in (maintainer-clean): New target. -Thu Aug 31 12:18:43 1995 Ian Lance Taylor <ian@cygnus.com> +1995-08-31 Ian Lance Taylor <ian@cygnus.com> * Makefile.in (bfd.h): Add additional #endif at end of bfd.h if __cplusplus is defined. -Tue Nov 29 16:13:34 1994 Doug Evans <dje@canuck.cygnus.com> +1994-11-29 Doug Evans <dje@canuck.cygnus.com> * chew.c (write_buffer): New argument `f', all callers changed. (stdout, stderr, print, drop, idrop): New forth words. * proto.str (COMMENT): New command. * doc.str (COMMENT): Likewise. -Mon Sep 12 11:44:17 1994 Ian Lance Taylor (ian@sanguine.cygnus.com) +1994-09-12 Ian Lance Taylor (ian@sanguine.cygnus.com) * Makefile.in (DOCFILES): Remove ctor.texi. (IPROTOS): Remove ctor.ip. @@ -349,7 +356,7 @@ Mon Sep 12 11:44:17 1994 Ian Lance Taylor (ian@sanguine.cygnus.com) $(MKDOC) run on $(srcdir)/../ctor.c. * bfd.texinfo (Constructors): Remove section. -Fri Sep 2 13:33:44 1994 Ken Raeburn (raeburn@cujo.cygnus.com) +1994-09-02 Ken Raeburn (raeburn@cujo.cygnus.com) * chew.c: Include assert.h. Added prototypes for most functions. Changed most uses of int to long. Do bounds checking on the @@ -371,46 +378,46 @@ Fri Sep 2 13:33:44 1994 Ken Raeburn (raeburn@cujo.cygnus.com) * doc.str, proto.str: Handle new commands SENUM, ENUM, ENUMX, ENUMEQ, ENUMEQX, ENUMDOC. -Wed Jan 12 18:37:12 1994 Ian Lance Taylor (ian@tweedledumb.cygnus.com) +1994-01-12 Ian Lance Taylor (ian@tweedledumb.cygnus.com) * bfd.texinfo: Added Linker Functions node. * Makefile.in (DOCFILES): Added linker.texi. (SRCDOC): Added linker.c. (linker.texi): New target. -Tue Jan 4 10:52:56 1994 Ian Lance Taylor (ian@tweedledumb.cygnus.com) +1994-01-04 Ian Lance Taylor (ian@tweedledumb.cygnus.com) * chew.c: Don't rely on a correct declaration of exit. (chew_exit): New function which just calls exit. (main): Use it. -Mon Jan 3 11:40:40 1994 Ian Lance Taylor (ian@tweedledumb.cygnus.com) +1994-01-03 Ian Lance Taylor (ian@tweedledumb.cygnus.com) * bfd.texinfo: Added Hash Tables node. * Makefile.in (DOCFILES): Added hash.texi. (SRCDOC): Added hash.c. (hash.texi): New target. -Thu Dec 30 16:57:04 1993 Ken Raeburn (raeburn@cujo.cygnus.com) +1993-12-30 Ken Raeburn (raeburn@cujo.cygnus.com) * Makefile.in: Delete all references to seclet.c, since it's just been deleted. Don't mention hash.c, linker.c, or genlink.h yet, since they don't contain documentation yet (hint, hint!). -Fri Nov 5 10:58:53 1993 David J. Mackenzie (djm@thepub.cygnus.com) +1993-11-05 David J. Mackenzie (djm@thepub.cygnus.com) * bfd.texinfo: Small cleanups. -Fri Nov 19 03:46:11 1993 Ken Raeburn (raeburn@cambridge.cygnus.com) +1993-11-19 Ken Raeburn (raeburn@cambridge.cygnus.com) * Makefile.in (archures.texi): Depends on $(MKDOC). -Tue Aug 10 14:22:39 1993 Ken Raeburn (raeburn@cambridge.cygnus.com) +1993-08-10 Ken Raeburn (raeburn@cambridge.cygnus.com) * bfd.texinfo (BFD back end): Don't include elfcode.texi, since it's empty now and that triggers a makeinfo bug. -Mon Aug 9 16:27:30 1993 Ken Raeburn (raeburn@cambridge.cygnus.com) +1993-08-09 Ken Raeburn (raeburn@cambridge.cygnus.com) * bfd.texinfo (BFD back end): New section on ELF, includes elf.texi and elfcode.texi. @@ -418,74 +425,74 @@ Mon Aug 9 16:27:30 1993 Ken Raeburn (raeburn@cambridge.cygnus.com) (SRCDOC): Include elfcode.h, elf.c. (elf.texi, elfcode.texi): New intermediate targets. -Thu Jun 24 13:48:13 1993 David J. Mackenzie (djm@thepub.cygnus.com) +1993-06-24 David J. Mackenzie (djm@thepub.cygnus.com) * Makefile.in (.c.o, chew.o): Put CFLAGS last. * bfdsumm.texi: New file, broken out of bfd.texinfo, to share with ld.texinfo. -Mon Jun 14 12:07:07 1993 david d `zoo' zuhn (zoo at rtl.cygnus.com) +1993-06-14 david d `zoo' zuhn (zoo at rtl.cygnus.com) * Makefile.in (install-info): remove parentdir cruft, -Wed Jun 9 16:00:32 1993 Jim Kingdon (kingdon@cygnus.com) +1993-06-09 Jim Kingdon (kingdon@cygnus.com) * Makefile.in (mostlyclean): Remove chew.o. -Tue May 25 14:46:58 1993 Ken Raeburn (raeburn@cambridge.cygnus.com) +1993-05-25 Ken Raeburn (raeburn@cambridge.cygnus.com) * Makefile.in (libbfd.h): Use elfcode.h, not elf32.c. -Mon May 24 15:50:07 1993 Ken Raeburn (raeburn@cygnus.com) +1993-05-24 Ken Raeburn (raeburn@cygnus.com) * chew.c (compile): Add a couple of missing casts. -Wed May 12 14:45:14 1993 Ian Lance Taylor (ian@cygnus.com) +1993-05-12 Ian Lance Taylor (ian@cygnus.com) * Makefile.in (CC_FOR_BUILD): New variable, define to be $(CC). (chew.o, $(MKDOC)): Build using CC_FOR_BUILD rather than CC, since it must run on the build machine. -Tue Apr 6 22:38:10 1993 John Gilmore (gnu@cygnus.com) +1993-04-07 John Gilmore (gnu@cygnus.com) * Makefile.in (chew): Don't compile from .c to executable in a single step; it puts a temporary .o filename into the executable, which makes multi-stage comparisons fail. Compile chew.c to chew.o, and link that, which makes identical executables every time. -Wed Mar 24 17:26:29 1993 david d `zoo' zuhn (zoo at poseidon.cygnus.com) +1993-03-24 david d `zoo' zuhn (zoo at poseidon.cygnus.com) * Makefile.in: fix typo (bfd.texinfo not bfd.texino) -Fri Mar 19 01:13:00 1993 Ken Raeburn (raeburn@kr-pc.cygnus.com) +1993-03-19 Ken Raeburn (raeburn@kr-pc.cygnus.com) * bfd.texinfo: Since BFD version number has been bumped, do same to "version number" on title page, and elsewhere. Should be fixed to extract real version number. -Tue Mar 16 12:15:13 1993 Per Bothner (bothner@rtl.cygnus.com) +1993-03-16 Per Bothner (bothner@rtl.cygnus.com) * Makefile.in: Add *clean rules. -Mon Jan 11 18:43:56 1993 Ian Lance Taylor (ian@tweedledumb.cygnus.com) +1993-01-11 Ian Lance Taylor (ian@tweedledumb.cygnus.com) * Makefile.in (libbfd.h): Removed duplicate init.c and libbfd.c. Added seclet.c. (bfd.h): Added dependency on bfd.c and seclet.c. Added seclet.c to build. -Thu Dec 17 19:35:43 1992 david d `zoo' zuhn (zoo at cirdan.cygnus.com) +1992-12-17 david d `zoo' zuhn (zoo at cirdan.cygnus.com) * Makefile.in: added dvi target, define and use $(TEXI2DVI) -Thu Dec 3 17:42:48 1992 Ken Raeburn (raeburn@cambridge.cygnus.com) +1992-12-03 Ken Raeburn (raeburn@cambridge.cygnus.com) * Makefile.in (TEXIDIR): New variable. (bfd.dvi): Look for bfd.texinfo in $(srcdir). Generate index. * bfd.texinfo: Minor doc fixes. -Thu Nov 5 03:13:55 1992 John Gilmore (gnu@cygnus.com) +1992-11-05 John Gilmore (gnu@cygnus.com) Cleanup: Replace all uses of EXFUN in the BFD sources, with PARAMS. @@ -493,70 +500,70 @@ Thu Nov 5 03:13:55 1992 John Gilmore (gnu@cygnus.com) (paramstuff): Replace exfunstuff with function to generate PARAMS. * proto.str: Use paramstuff rather than exfunstuff. -Mon Aug 17 12:40:32 1992 Steve Chamberlain (sac@thepub.cygnus.com) +1992-08-17 Steve Chamberlain (sac@thepub.cygnus.com) * chew.c: various patches provided by Howard Chu. -Fri Jun 19 18:59:54 1992 John Gilmore (gnu at cygnus.com) +1992-06-19 John Gilmore (gnu at cygnus.com) * Makefile.in (libbfd.h): Add elf.c as a source of prototypes. -Mon May 11 18:55:59 1992 John Gilmore (gnu at cygnus.com) +1992-05-11 John Gilmore (gnu at cygnus.com) * chew.c: exit() should be declared by config files, not by portable source code. Its type could be int or void function. -Mon May 4 13:45:57 1992 K. Richard Pixley (rich@rtl.cygnus.com) +1992-05-04 K. Richard Pixley (rich@rtl.cygnus.com) * Makefile.in: another CFLAGS correction. -Tue Apr 28 10:21:32 1992 K. Richard Pixley (rich@rtl.cygnus.com) +1992-04-28 K. Richard Pixley (rich@rtl.cygnus.com) * Makefile.in: Do the CFLAGS thing. -Fri Apr 10 22:34:52 1992 Fred Fish (fnf@cygnus.com) +1992-04-11 Fred Fish (fnf@cygnus.com) * Makefile.in (MINUS_G): Add macro and default to -g. -Fri Mar 6 18:53:18 1992 Steve Chamberlain (sac@thepub.cygnus.com) +1992-03-06 Steve Chamberlain (sac@thepub.cygnus.com) * chew.c: now has -w switch turn on warnings -Wed Feb 26 18:04:40 1992 K. Richard Pixley (rich@cygnus.com) +1992-02-26 K. Richard Pixley (rich@cygnus.com) * Makefile.in, configure.in: removed traces of namesubdir, -subdirs, $(subdir), $(unsubdir), some rcs triggers. Forced copyrights to '92, changed some from Cygnus to FSF. -Tue Dec 10 22:11:05 1991 K. Richard Pixley (rich at rtl.cygnus.com) +1991-12-10 K. Richard Pixley (rich at rtl.cygnus.com) * Makefile.in: build chew into the current directory. Complete the MKDOC macro transition. -Tue Dec 10 08:26:28 1991 Steve Chamberlain (sac at rtl.cygnus.com) +1991-12-10 Steve Chamberlain (sac at rtl.cygnus.com) * chew.c: don't core dump when can't open file * Makefile.in: get proto.str from the right place when built in odd directories -Tue Dec 10 04:07:25 1991 K. Richard Pixley (rich at rtl.cygnus.com) +1991-12-10 K. Richard Pixley (rich at rtl.cygnus.com) * Makefile.in: infodir belongs in datadir. -Sat Dec 7 17:01:23 1991 Steve Chamberlain (sac at rtl.cygnus.com) +1991-12-07 Steve Chamberlain (sac at rtl.cygnus.com) * chew.c: Much modified * proto.str, doc.str: New files for extracting to product prototypes and documents respectively. -Fri Dec 6 22:57:12 1991 K. Richard Pixley (rich at rtl.cygnus.com) +1991-12-06 K. Richard Pixley (rich at rtl.cygnus.com) * Makefile.in: added standards.text support, host/site/target inclusion hooks, install using INSTALL_DATA rather than cp, don't echo on install. -Thu Dec 5 22:46:17 1991 K. Richard Pixley (rich at rtl.cygnus.com) +1991-12-05 K. Richard Pixley (rich at rtl.cygnus.com) * Makefile.in: idestdir and ddestdir go away. Added copyrights and shift gpl to v2. Added ChangeLog if it didn't exist. docdir diff --git a/bfd/doc/bfd.texinfo b/bfd/doc/bfd.texinfo index f12222e..d6a427f 100644 --- a/bfd/doc/bfd.texinfo +++ b/bfd/doc/bfd.texinfo @@ -1,6 +1,6 @@ \input texinfo.tex @setfilename bfd.info -@c Copyright 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1997, 2000 +@c Copyright 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1997, 2000, 2003 @c Free Software Foundation, Inc. @c @tex @@ -30,14 +30,14 @@ END-INFO-DIR-ENTRY @ifinfo This file documents the BFD library. -Copyright (C) 1991, 2000, 2001 Free Software Foundation, Inc. +Copyright (C) 1991, 2000, 2001, 2003 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the - section entitled "GNU Free Documentation License". + section entitled ``GNU Free Documentation License''. @ignore Permission is granted to process this file through Tex and print the @@ -75,14 +75,14 @@ notice identical to this one except for the removal of this paragraph @end tex @vskip 0pt plus 1filll -Copyright @copyright{} 1991, 2001 Free Software Foundation, Inc. +Copyright @copyright{} 1991, 2001, 2003 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the - section entitled "GNU Free Documentation License". + section entitled ``GNU Free Documentation License''. @end titlepage @end iftex @@ -170,17 +170,17 @@ For example, this sequence does what you would probably expect: return the number of sections in an object file attached to a BFD @code{abfd}. -@lisp +@example @c @cartouche #include "bfd.h" -unsigned int number_of_sections(abfd) +unsigned int number_of_sections (abfd) bfd *abfd; @{ - return bfd_count_sections(abfd); + return bfd_count_sections (abfd); @} @c @end cartouche -@end lisp +@end example The abstraction used within BFD is that an object file has: @@ -205,7 +205,7 @@ IEEE-695. @include bfdsumm.texi @node BFD front end, BFD back ends, Overview, Top -@chapter BFD front end +@chapter BFD Front End @include bfdt.texi @include bfdio.texi @@ -228,7 +228,7 @@ IEEE-695. @end menu @node Memory Usage, Initialization, BFD front end, BFD front end -@section Memory usage +@section Memory Usage BFD keeps all of its internal structures in obstacks. There is one obstack per open BFD file, into which the current state is stored. When a BFD is closed, the obstack is deleted, and so everything which has been @@ -324,370 +324,9 @@ All of BFD lives in one directory. @include mmo.texi @node GNU Free Documentation License, Index, BFD back ends, Top -@chapter GNU Free Documentation License -@cindex GNU Free Documentation License - - GNU Free Documentation License - - Version 1.1, March 2000 - - Copyright (C) 2000 Free Software Foundation, Inc. - 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA - - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - -0. PREAMBLE - -The purpose of this License is to make a manual, textbook, or other -written document "free" in the sense of freedom: to assure everyone -the effective freedom to copy and redistribute it, with or without -modifying it, either commercially or noncommercially. Secondarily, -this License preserves for the author and publisher a way to get -credit for their work, while not being considered responsible for -modifications made by others. - -This License is a kind of "copyleft", which means that derivative -works of the document must themselves be free in the same sense. It -complements the GNU General Public License, which is a copyleft -license designed for free software. - -We have designed this License in order to use it for manuals for free -software, because free software needs free documentation: a free -program should come with manuals providing the same freedoms that the -software does. But this License is not limited to software manuals; -it can be used for any textual work, regardless of subject matter or -whether it is published as a printed book. We recommend this License -principally for works whose purpose is instruction or reference. - - -1. APPLICABILITY AND DEFINITIONS - -This License applies to any manual or other work that contains a -notice placed by the copyright holder saying it can be distributed -under the terms of this License. The "Document", below, refers to any -such manual or work. Any member of the public is a licensee, and is -addressed as "you". - -A "Modified Version" of the Document means any work containing the -Document or a portion of it, either copied verbatim, or with -modifications and/or translated into another language. - -A "Secondary Section" is a named appendix or a front-matter section of -the Document that deals exclusively with the relationship of the -publishers or authors of the Document to the Document's overall subject -(or to related matters) and contains nothing that could fall directly -within that overall subject. (For example, if the Document is in part a -textbook of mathematics, a Secondary Section may not explain any -mathematics.) The relationship could be a matter of historical -connection with the subject or with related matters, or of legal, -commercial, philosophical, ethical or political position regarding -them. - -The "Invariant Sections" are certain Secondary Sections whose titles -are designated, as being those of Invariant Sections, in the notice -that says that the Document is released under this License. - -The "Cover Texts" are certain short passages of text that are listed, -as Front-Cover Texts or Back-Cover Texts, in the notice that says that -the Document is released under this License. - -A "Transparent" copy of the Document means a machine-readable copy, -represented in a format whose specification is available to the -general public, whose contents can be viewed and edited directly and -straightforwardly with generic text editors or (for images composed of -pixels) generic paint programs or (for drawings) some widely available -drawing editor, and that is suitable for input to text formatters or -for automatic translation to a variety of formats suitable for input -to text formatters. A copy made in an otherwise Transparent file -format whose markup has been designed to thwart or discourage -subsequent modification by readers is not Transparent. A copy that is -not "Transparent" is called "Opaque". - -Examples of suitable formats for Transparent copies include plain -ASCII without markup, Texinfo input format, LaTeX input format, SGML -or XML using a publicly available DTD, and standard-conforming simple -HTML designed for human modification. Opaque formats include -PostScript, PDF, proprietary formats that can be read and edited only -by proprietary word processors, SGML or XML for which the DTD and/or -processing tools are not generally available, and the -machine-generated HTML produced by some word processors for output -purposes only. - -The "Title Page" means, for a printed book, the title page itself, -plus such following pages as are needed to hold, legibly, the material -this License requires to appear in the title page. For works in -formats which do not have any title page as such, "Title Page" means -the text near the most prominent appearance of the work's title, -preceding the beginning of the body of the text. - - -2. VERBATIM COPYING - -You may copy and distribute the Document in any medium, either -commercially or noncommercially, provided that this License, the -copyright notices, and the license notice saying this License applies -to the Document are reproduced in all copies, and that you add no other -conditions whatsoever to those of this License. You may not use -technical measures to obstruct or control the reading or further -copying of the copies you make or distribute. However, you may accept -compensation in exchange for copies. If you distribute a large enough -number of copies you must also follow the conditions in section 3. - -You may also lend copies, under the same conditions stated above, and -you may publicly display copies. - - -3. COPYING IN QUANTITY - -If you publish printed copies of the Document numbering more than 100, -and the Document's license notice requires Cover Texts, you must enclose -the copies in covers that carry, clearly and legibly, all these Cover -Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on -the back cover. Both covers must also clearly and legibly identify -you as the publisher of these copies. The front cover must present -the full title with all words of the title equally prominent and -visible. You may add other material on the covers in addition. -Copying with changes limited to the covers, as long as they preserve -the title of the Document and satisfy these conditions, can be treated -as verbatim copying in other respects. - -If the required texts for either cover are too voluminous to fit -legibly, you should put the first ones listed (as many as fit -reasonably) on the actual cover, and continue the rest onto adjacent -pages. - -If you publish or distribute Opaque copies of the Document numbering -more than 100, you must either include a machine-readable Transparent -copy along with each Opaque copy, or state in or with each Opaque copy -a publicly-accessible computer-network location containing a complete -Transparent copy of the Document, free of added material, which the -general network-using public has access to download anonymously at no -charge using public-standard network protocols. If you use the latter -option, you must take reasonably prudent steps, when you begin -distribution of Opaque copies in quantity, to ensure that this -Transparent copy will remain thus accessible at the stated location -until at least one year after the last time you distribute an Opaque -copy (directly or through your agents or retailers) of that edition to -the public. - -It is requested, but not required, that you contact the authors of the -Document well before redistributing any large number of copies, to give -them a chance to provide you with an updated version of the Document. - - -4. MODIFICATIONS - -You may copy and distribute a Modified Version of the Document under -the conditions of sections 2 and 3 above, provided that you release -the Modified Version under precisely this License, with the Modified -Version filling the role of the Document, thus licensing distribution -and modification of the Modified Version to whoever possesses a copy -of it. In addition, you must do these things in the Modified Version: - -A. Use in the Title Page (and on the covers, if any) a title distinct - from that of the Document, and from those of previous versions - (which should, if there were any, be listed in the History section - of the Document). You may use the same title as a previous version - if the original publisher of that version gives permission. -B. List on the Title Page, as authors, one or more persons or entities - responsible for authorship of the modifications in the Modified - Version, together with at least five of the principal authors of the - Document (all of its principal authors, if it has less than five). -C. State on the Title page the name of the publisher of the - Modified Version, as the publisher. -D. Preserve all the copyright notices of the Document. -E. Add an appropriate copyright notice for your modifications - adjacent to the other copyright notices. -F. Include, immediately after the copyright notices, a license notice - giving the public permission to use the Modified Version under the - terms of this License, in the form shown in the Addendum below. -G. Preserve in that license notice the full lists of Invariant Sections - and required Cover Texts given in the Document's license notice. -H. Include an unaltered copy of this License. -I. Preserve the section entitled "History", and its title, and add to - it an item stating at least the title, year, new authors, and - publisher of the Modified Version as given on the Title Page. If - there is no section entitled "History" in the Document, create one - stating the title, year, authors, and publisher of the Document as - given on its Title Page, then add an item describing the Modified - Version as stated in the previous sentence. -J. Preserve the network location, if any, given in the Document for - public access to a Transparent copy of the Document, and likewise - the network locations given in the Document for previous versions - it was based on. These may be placed in the "History" section. - You may omit a network location for a work that was published at - least four years before the Document itself, or if the original - publisher of the version it refers to gives permission. -K. In any section entitled "Acknowledgements" or "Dedications", - preserve the section's title, and preserve in the section all the - substance and tone of each of the contributor acknowledgements - and/or dedications given therein. -L. Preserve all the Invariant Sections of the Document, - unaltered in their text and in their titles. Section numbers - or the equivalent are not considered part of the section titles. -M. Delete any section entitled "Endorsements". Such a section - may not be included in the Modified Version. -N. Do not retitle any existing section as "Endorsements" - or to conflict in title with any Invariant Section. - -If the Modified Version includes new front-matter sections or -appendices that qualify as Secondary Sections and contain no material -copied from the Document, you may at your option designate some or all -of these sections as invariant. To do this, add their titles to the -list of Invariant Sections in the Modified Version's license notice. -These titles must be distinct from any other section titles. - -You may add a section entitled "Endorsements", provided it contains -nothing but endorsements of your Modified Version by various -parties--for example, statements of peer review or that the text has -been approved by an organization as the authoritative definition of a -standard. - -You may add a passage of up to five words as a Front-Cover Text, and a -passage of up to 25 words as a Back-Cover Text, to the end of the list -of Cover Texts in the Modified Version. Only one passage of -Front-Cover Text and one of Back-Cover Text may be added by (or -through arrangements made by) any one entity. If the Document already -includes a cover text for the same cover, previously added by you or -by arrangement made by the same entity you are acting on behalf of, -you may not add another; but you may replace the old one, on explicit -permission from the previous publisher that added the old one. - -The author(s) and publisher(s) of the Document do not by this License -give permission to use their names for publicity for or to assert or -imply endorsement of any Modified Version. - - -5. COMBINING DOCUMENTS - -You may combine the Document with other documents released under this -License, under the terms defined in section 4 above for modified -versions, provided that you include in the combination all of the -Invariant Sections of all of the original documents, unmodified, and -list them all as Invariant Sections of your combined work in its -license notice. - -The combined work need only contain one copy of this License, and -multiple identical Invariant Sections may be replaced with a single -copy. If there are multiple Invariant Sections with the same name but -different contents, make the title of each such section unique by -adding at the end of it, in parentheses, the name of the original -author or publisher of that section if known, or else a unique number. -Make the same adjustment to the section titles in the list of -Invariant Sections in the license notice of the combined work. - -In the combination, you must combine any sections entitled "History" -in the various original documents, forming one section entitled -"History"; likewise combine any sections entitled "Acknowledgements", -and any sections entitled "Dedications". You must delete all sections -entitled "Endorsements." - - -6. COLLECTIONS OF DOCUMENTS - -You may make a collection consisting of the Document and other documents -released under this License, and replace the individual copies of this -License in the various documents with a single copy that is included in -the collection, provided that you follow the rules of this License for -verbatim copying of each of the documents in all other respects. - -You may extract a single document from such a collection, and distribute -it individually under this License, provided you insert a copy of this -License into the extracted document, and follow this License in all -other respects regarding verbatim copying of that document. - - -7. AGGREGATION WITH INDEPENDENT WORKS - -A compilation of the Document or its derivatives with other separate -and independent documents or works, in or on a volume of a storage or -distribution medium, does not as a whole count as a Modified Version -of the Document, provided no compilation copyright is claimed for the -compilation. Such a compilation is called an "aggregate", and this -License does not apply to the other self-contained works thus compiled -with the Document, on account of their being thus compiled, if they -are not themselves derivative works of the Document. - -If the Cover Text requirement of section 3 is applicable to these -copies of the Document, then if the Document is less than one quarter -of the entire aggregate, the Document's Cover Texts may be placed on -covers that surround only the Document within the aggregate. -Otherwise they must appear on covers around the whole aggregate. - - -8. TRANSLATION - -Translation is considered a kind of modification, so you may -distribute translations of the Document under the terms of section 4. -Replacing Invariant Sections with translations requires special -permission from their copyright holders, but you may include -translations of some or all Invariant Sections in addition to the -original versions of these Invariant Sections. You may include a -translation of this License provided that you also include the -original English version of this License. In case of a disagreement -between the translation and the original English version of this -License, the original English version will prevail. - - -9. TERMINATION - -You may not copy, modify, sublicense, or distribute the Document except -as expressly provided for under this License. Any other attempt to -copy, modify, sublicense or distribute the Document is void, and will -automatically terminate your rights under this License. However, -parties who have received copies, or rights, from you under this -License will not have their licenses terminated so long as such -parties remain in full compliance. - - -10. FUTURE REVISIONS OF THIS LICENSE - -The Free Software Foundation may publish new, revised versions -of the GNU Free Documentation License from time to time. Such new -versions will be similar in spirit to the present version, but may -differ in detail to address new problems or concerns. See -http://www.gnu.org/copyleft/. - -Each version of the License is given a distinguishing version number. -If the Document specifies that a particular numbered version of this -License "or any later version" applies to it, you have the option of -following the terms and conditions either of that specified version or -of any later version that has been published (not as a draft) by the -Free Software Foundation. If the Document does not specify a version -number of this License, you may choose any version ever published (not -as a draft) by the Free Software Foundation. - - -ADDENDUM: How to use this License for your documents - -To use this License in a document you have written, include a copy of -the License in the document and put the following copyright and -license notices just after the title page: - -@smallexample - Copyright (c) YEAR YOUR NAME. - Permission is granted to copy, distribute and/or modify this document - under the terms of the GNU Free Documentation License, Version 1.1 - or any later version published by the Free Software Foundation; - with the Invariant Sections being LIST THEIR TITLES, with the - Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. - A copy of the license is included in the section entitled "GNU - Free Documentation License". -@end smallexample - -If you have no Invariant Sections, write "with no Invariant Sections" -instead of saying which ones are invariant. If you have no -Front-Cover Texts, write "no Front-Cover Texts" instead of -"Front-Cover Texts being LIST"; likewise for Back-Cover Texts. - -If your document contains nontrivial examples of program code, we -recommend releasing these examples in parallel under your choice of -free software license, such as the GNU General Public License, -to permit their use in free software. - -@node Index, , GNU Free Documentation License , Top +@include fdl.texi + +@node Index, , GNU Free Documentation License, Top @unnumbered Index @printindex cp diff --git a/bfd/doc/fdl.texi b/bfd/doc/fdl.texi new file mode 100644 index 0000000..176233c --- /dev/null +++ b/bfd/doc/fdl.texi @@ -0,0 +1,366 @@ +@c -*-texinfo-*- +@appendix GNU Free Documentation License +@center Version 1.1, March 2000 + +@display +Copyright (C) 2000, Free Software Foundation, Inc. +59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + +Everyone is permitted to copy and distribute verbatim copies +of this license document, but changing it is not allowed. +@end display +@sp 1 +@enumerate 0 +@item +PREAMBLE + +The purpose of this License is to make a manual, textbook, or other +written document ``free'' in the sense of freedom: to assure everyone +the effective freedom to copy and redistribute it, with or without +modifying it, either commercially or noncommercially. Secondarily, +this License preserves for the author and publisher a way to get +credit for their work, while not being considered responsible for +modifications made by others. + +This License is a kind of ``copyleft'', which means that derivative +works of the document must themselves be free in the same sense. It +complements the GNU General Public License, which is a copyleft +license designed for free software. + +We have designed this License in order to use it for manuals for free +software, because free software needs free documentation: a free +program should come with manuals providing the same freedoms that the +software does. But this License is not limited to software manuals; +it can be used for any textual work, regardless of subject matter or +whether it is published as a printed book. We recommend this License +principally for works whose purpose is instruction or reference. + +@sp 1 +@item +APPLICABILITY AND DEFINITIONS + +This License applies to any manual or other work that contains a +notice placed by the copyright holder saying it can be distributed +under the terms of this License. The ``Document'', below, refers to any +such manual or work. Any member of the public is a licensee, and is +addressed as ``you.'' + +A ``Modified Version'' of the Document means any work containing the +Document or a portion of it, either copied verbatim, or with +modifications and/or translated into another language. + +A ``Secondary Section'' is a named appendix or a front-matter section of +the Document that deals exclusively with the relationship of the +publishers or authors of the Document to the Document's overall subject +(or to related matters) and contains nothing that could fall directly +within that overall subject. (For example, if the Document is in part a +textbook of mathematics, a Secondary Section may not explain any +mathematics.) The relationship could be a matter of historical +connection with the subject or with related matters, or of legal, +commercial, philosophical, ethical or political position regarding +them. + +The ``Invariant Sections'' are certain Secondary Sections whose titles +are designated, as being those of Invariant Sections, in the notice +that says that the Document is released under this License. + +The ``Cover Texts'' are certain short passages of text that are listed, +as Front-Cover Texts or Back-Cover Texts, in the notice that says that +the Document is released under this License. + +A ``Transparent'' copy of the Document means a machine-readable copy, +represented in a format whose specification is available to the +general public, whose contents can be viewed and edited directly and +straightforwardly with generic text editors or (for images composed of +pixels) generic paint programs or (for drawings) some widely available +drawing editor, and that is suitable for input to text formatters or +for automatic translation to a variety of formats suitable for input +to text formatters. A copy made in an otherwise Transparent file +format whose markup has been designed to thwart or discourage +subsequent modification by readers is not Transparent. A copy that is +not ``Transparent'' is called ``Opaque.'' + +Examples of suitable formats for Transparent copies include plain +ASCII without markup, Texinfo input format, LaTeX input format, SGML +or XML using a publicly available DTD, and standard-conforming simple +HTML designed for human modification. Opaque formats include +PostScript, PDF, proprietary formats that can be read and edited only +by proprietary word processors, SGML or XML for which the DTD and/or +processing tools are not generally available, and the +machine-generated HTML produced by some word processors for output +purposes only. + +The ``Title Page'' means, for a printed book, the title page itself, +plus such following pages as are needed to hold, legibly, the material +this License requires to appear in the title page. For works in +formats which do not have any title page as such, ``Title Page'' means +the text near the most prominent appearance of the work's title, +preceding the beginning of the body of the text. +@sp 1 +@item +VERBATIM COPYING + +You may copy and distribute the Document in any medium, either +commercially or noncommercially, provided that this License, the +copyright notices, and the license notice saying this License applies +to the Document are reproduced in all copies, and that you add no other +conditions whatsoever to those of this License. You may not use +technical measures to obstruct or control the reading or further +copying of the copies you make or distribute. However, you may accept +compensation in exchange for copies. If you distribute a large enough +number of copies you must also follow the conditions in section 3. + +You may also lend copies, under the same conditions stated above, and +you may publicly display copies. +@sp 1 +@item +COPYING IN QUANTITY + +If you publish printed copies of the Document numbering more than 100, +and the Document's license notice requires Cover Texts, you must enclose +the copies in covers that carry, clearly and legibly, all these Cover +Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on +the back cover. Both covers must also clearly and legibly identify +you as the publisher of these copies. The front cover must present +the full title with all words of the title equally prominent and +visible. You may add other material on the covers in addition. +Copying with changes limited to the covers, as long as they preserve +the title of the Document and satisfy these conditions, can be treated +as verbatim copying in other respects. + +If the required texts for either cover are too voluminous to fit +legibly, you should put the first ones listed (as many as fit +reasonably) on the actual cover, and continue the rest onto adjacent +pages. + +If you publish or distribute Opaque copies of the Document numbering +more than 100, you must either include a machine-readable Transparent +copy along with each Opaque copy, or state in or with each Opaque copy +a publicly-accessible computer-network location containing a complete +Transparent copy of the Document, free of added material, which the +general network-using public has access to download anonymously at no +charge using public-standard network protocols. If you use the latter +option, you must take reasonably prudent steps, when you begin +distribution of Opaque copies in quantity, to ensure that this +Transparent copy will remain thus accessible at the stated location +until at least one year after the last time you distribute an Opaque +copy (directly or through your agents or retailers) of that edition to +the public. + +It is requested, but not required, that you contact the authors of the +Document well before redistributing any large number of copies, to give +them a chance to provide you with an updated version of the Document. +@sp 1 +@item +MODIFICATIONS + +You may copy and distribute a Modified Version of the Document under +the conditions of sections 2 and 3 above, provided that you release +the Modified Version under precisely this License, with the Modified +Version filling the role of the Document, thus licensing distribution +and modification of the Modified Version to whoever possesses a copy +of it. In addition, you must do these things in the Modified Version: + +A. Use in the Title Page (and on the covers, if any) a title distinct + from that of the Document, and from those of previous versions + (which should, if there were any, be listed in the History section + of the Document). You may use the same title as a previous version + if the original publisher of that version gives permission.@* +B. List on the Title Page, as authors, one or more persons or entities + responsible for authorship of the modifications in the Modified + Version, together with at least five of the principal authors of the + Document (all of its principal authors, if it has less than five).@* +C. State on the Title page the name of the publisher of the + Modified Version, as the publisher.@* +D. Preserve all the copyright notices of the Document.@* +E. Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices.@* +F. Include, immediately after the copyright notices, a license notice + giving the public permission to use the Modified Version under the + terms of this License, in the form shown in the Addendum below.@* +G. Preserve in that license notice the full lists of Invariant Sections + and required Cover Texts given in the Document's license notice.@* +H. Include an unaltered copy of this License.@* +I. Preserve the section entitled ``History'', and its title, and add to + it an item stating at least the title, year, new authors, and + publisher of the Modified Version as given on the Title Page. If + there is no section entitled ``History'' in the Document, create one + stating the title, year, authors, and publisher of the Document as + given on its Title Page, then add an item describing the Modified + Version as stated in the previous sentence.@* +J. Preserve the network location, if any, given in the Document for + public access to a Transparent copy of the Document, and likewise + the network locations given in the Document for previous versions + it was based on. These may be placed in the ``History'' section. + You may omit a network location for a work that was published at + least four years before the Document itself, or if the original + publisher of the version it refers to gives permission.@* +K. In any section entitled ``Acknowledgements'' or ``Dedications'', + preserve the section's title, and preserve in the section all the + substance and tone of each of the contributor acknowledgements + and/or dedications given therein.@* +L. Preserve all the Invariant Sections of the Document, + unaltered in their text and in their titles. Section numbers + or the equivalent are not considered part of the section titles.@* +M. Delete any section entitled ``Endorsements.'' Such a section + may not be included in the Modified Version.@* +N. Do not retitle any existing section as ``Endorsements'' + or to conflict in title with any Invariant Section.@* +@sp 1 +If the Modified Version includes new front-matter sections or +appendices that qualify as Secondary Sections and contain no material +copied from the Document, you may at your option designate some or all +of these sections as invariant. To do this, add their titles to the +list of Invariant Sections in the Modified Version's license notice. +These titles must be distinct from any other section titles. + +You may add a section entitled ``Endorsements'', provided it contains +nothing but endorsements of your Modified Version by various +parties--for example, statements of peer review or that the text has +been approved by an organization as the authoritative definition of a +standard. + +You may add a passage of up to five words as a Front-Cover Text, and a +passage of up to 25 words as a Back-Cover Text, to the end of the list +of Cover Texts in the Modified Version. Only one passage of +Front-Cover Text and one of Back-Cover Text may be added by (or +through arrangements made by) any one entity. If the Document already +includes a cover text for the same cover, previously added by you or +by arrangement made by the same entity you are acting on behalf of, +you may not add another; but you may replace the old one, on explicit +permission from the previous publisher that added the old one. + +The author(s) and publisher(s) of the Document do not by this License +give permission to use their names for publicity for or to assert or +imply endorsement of any Modified Version. +@sp 1 +@item +COMBINING DOCUMENTS + +You may combine the Document with other documents released under this +License, under the terms defined in section 4 above for modified +versions, provided that you include in the combination all of the +Invariant Sections of all of the original documents, unmodified, and +list them all as Invariant Sections of your combined work in its +license notice. + +The combined work need only contain one copy of this License, and +multiple identical Invariant Sections may be replaced with a single +copy. If there are multiple Invariant Sections with the same name but +different contents, make the title of each such section unique by +adding at the end of it, in parentheses, the name of the original +author or publisher of that section if known, or else a unique number. +Make the same adjustment to the section titles in the list of +Invariant Sections in the license notice of the combined work. + +In the combination, you must combine any sections entitled ``History'' +in the various original documents, forming one section entitled +``History''; likewise combine any sections entitled ``Acknowledgements'', +and any sections entitled ``Dedications.'' You must delete all sections +entitled ``Endorsements.'' +@sp 1 +@item +COLLECTIONS OF DOCUMENTS + +You may make a collection consisting of the Document and other documents +released under this License, and replace the individual copies of this +License in the various documents with a single copy that is included in +the collection, provided that you follow the rules of this License for +verbatim copying of each of the documents in all other respects. + +You may extract a single document from such a collection, and distribute +it individually under this License, provided you insert a copy of this +License into the extracted document, and follow this License in all +other respects regarding verbatim copying of that document. +@sp 1 +@item +AGGREGATION WITH INDEPENDENT WORKS + +A compilation of the Document or its derivatives with other separate +and independent documents or works, in or on a volume of a storage or +distribution medium, does not as a whole count as a Modified Version +of the Document, provided no compilation copyright is claimed for the +compilation. Such a compilation is called an ``aggregate'', and this +License does not apply to the other self-contained works thus compiled +with the Document, on account of their being thus compiled, if they +are not themselves derivative works of the Document. + +If the Cover Text requirement of section 3 is applicable to these +copies of the Document, then if the Document is less than one quarter +of the entire aggregate, the Document's Cover Texts may be placed on +covers that surround only the Document within the aggregate. +Otherwise they must appear on covers around the whole aggregate. +@sp 1 +@item +TRANSLATION + +Translation is considered a kind of modification, so you may +distribute translations of the Document under the terms of section 4. +Replacing Invariant Sections with translations requires special +permission from their copyright holders, but you may include +translations of some or all Invariant Sections in addition to the +original versions of these Invariant Sections. You may include a +translation of this License provided that you also include the +original English version of this License. In case of a disagreement +between the translation and the original English version of this +License, the original English version will prevail. +@sp 1 +@item +TERMINATION + +You may not copy, modify, sublicense, or distribute the Document except +as expressly provided for under this License. Any other attempt to +copy, modify, sublicense or distribute the Document is void, and will +automatically terminate your rights under this License. However, +parties who have received copies, or rights, from you under this +License will not have their licenses terminated so long as such +parties remain in full compliance. +@sp 1 +@item +FUTURE REVISIONS OF THIS LICENSE + +The Free Software Foundation may publish new, revised versions +of the GNU Free Documentation License from time to time. Such new +versions will be similar in spirit to the present version, but may +differ in detail to address new problems or concerns. See +http://www.gnu.org/copyleft/. + +Each version of the License is given a distinguishing version number. +If the Document specifies that a particular numbered version of this +License ``or any later version'' applies to it, you have the option of +following the terms and conditions either of that specified version or +of any later version that has been published (not as a draft) by the +Free Software Foundation. If the Document does not specify a version +number of this License, you may choose any version ever published (not +as a draft) by the Free Software Foundation. + +@end enumerate + +@unnumberedsec ADDENDUM: How to use this License for your documents + +To use this License in a document you have written, include a copy of +the License in the document and put the following copyright and +license notices just after the title page: + +@smallexample +@group +Copyright (C) @var{year} @var{your name}. +Permission is granted to copy, distribute and/or modify this document +under the terms of the GNU Free Documentation License, Version 1.1 +or any later version published by the Free Software Foundation; +with the Invariant Sections being @var{list their titles}, with the +Front-Cover Texts being @var{list}, and with the Back-Cover Texts being @var{list}. +A copy of the license is included in the section entitled "GNU +Free Documentation License." +@end group +@end smallexample + +If you have no Invariant Sections, write ``with no Invariant Sections'' +instead of saying which ones are invariant. If you have no +Front-Cover Texts, write ``no Front-Cover Texts'' instead of +``Front-Cover Texts being @var{list}''; likewise for Back-Cover Texts. + +If your document contains nontrivial examples of program code, we +recommend releasing these examples in parallel under your choice of +free software license, such as the GNU General Public License, +to permit their use in free software. |