bfd.texinfo revision 77298
1\input texinfo.tex 2@setfilename bfd.info 3@c $Id: bfd.texinfo,v 1.2 2000/11/15 18:24:49 nickc Exp $ 4@tex 5% NOTE LOCAL KLUGE TO AVOID TOO MUCH WHITESPACE 6\global\long\def\example{% 7\begingroup 8\let\aboveenvbreak=\par 9\let\afterenvbreak=\par 10\parskip=0pt 11\lisp} 12\global\long\def\Eexample{% 13\Elisp 14\endgroup 15\vskip -\parskip% to cancel out effect of following \par 16} 17@end tex 18@synindex fn cp 19 20@ifinfo 21@format 22START-INFO-DIR-ENTRY 23* Bfd: (bfd). The Binary File Descriptor library. 24END-INFO-DIR-ENTRY 25@end format 26@end ifinfo 27 28@ifinfo 29This file documents the BFD library. 30 31Copyright (C) 1991, 2000 Free Software Foundation, Inc. 32 33 Permission is granted to copy, distribute and/or modify this document 34 under the terms of the GNU Free Documentation License, Version 1.1 35 or any later version published by the Free Software Foundation; 36 with no Invariant Sections, with no Front-Cover Texts, and with no 37 Back-Cover Texts. A copy of the license is included in the 38 section entitled "GNU Free Documentation License". 39 40@ignore 41Permission is granted to process this file through Tex and print the 42results, provided the printed document carries copying permission 43notice identical to this one except for the removal of this paragraph 44(this paragraph not being relevant to the printed manual). 45 46@end ignore 47@end ifinfo 48@iftex 49@c@finalout 50@setchapternewpage on 51@c@setchapternewpage odd 52@settitle LIB BFD, the Binary File Descriptor Library 53@titlepage 54@title{libbfd} 55@subtitle{The Binary File Descriptor Library} 56@sp 1 57@subtitle First Edition---BFD version < 3.0 58@subtitle April 1991 59@author {Steve Chamberlain} 60@author {Cygnus Support} 61@page 62 63@tex 64\def\$#1${{#1}} % Kluge: collect RCS revision info without $...$ 65\xdef\manvers{\$Revision: 1.2 $} % For use in headers, footers too 66{\parskip=0pt 67\hfill Cygnus Support\par 68\hfill sac\@cygnus.com\par 69\hfill {\it BFD}, \manvers\par 70\hfill \TeX{}info \texinfoversion\par 71} 72\global\parindent=0pt % Steve likes it this way 73@end tex 74 75@vskip 0pt plus 1filll 76Copyright @copyright{} 1991 Free Software Foundation, Inc. 77 78 Permission is granted to copy, distribute and/or modify this document 79 under the terms of the GNU Free Documentation License, Version 1.1 80 or any later version published by the Free Software Foundation; 81 with no Invariant Sections, with no Front-Cover Texts, and with no 82 Back-Cover Texts. A copy of the license is included in the 83 section entitled "GNU Free Documentation License". 84 85@end titlepage 86@end iftex 87 88@node Top, Overview, (dir), (dir) 89@ifinfo 90This file documents the binary file descriptor library libbfd. 91@end ifinfo 92 93@menu 94* Overview:: Overview of BFD 95* BFD front end:: BFD front end 96* BFD back ends:: BFD back ends 97* GNU Free Documentation License:: GNU Free Documentation License 98* Index:: Index 99@end menu 100 101@node Overview, BFD front end, Top, Top 102@chapter Introduction 103@cindex BFD 104@cindex what is it? 105BFD is a package which allows applications to use the 106same routines to operate on object files whatever the object file 107format. A new object file format can be supported simply by 108creating a new BFD back end and adding it to the library. 109 110BFD is split into two parts: the front end, and the back ends (one for 111each object file format). 112@itemize @bullet 113@item The front end of BFD provides the interface to the user. It manages 114memory and various canonical data structures. The front end also 115decides which back end to use and when to call back end routines. 116@item The back ends provide BFD its view of the real world. Each back 117end provides a set of calls which the BFD front end can use to maintain 118its canonical form. The back ends also may keep around information for 119their own use, for greater efficiency. 120@end itemize 121@menu 122* History:: History 123* How It Works:: How It Works 124* What BFD Version 2 Can Do:: What BFD Version 2 Can Do 125@end menu 126 127@node History, How It Works, Overview, Overview 128@section History 129 130One spur behind BFD was the desire, on the part of the GNU 960 team at 131Intel Oregon, for interoperability of applications on their COFF and 132b.out file formats. Cygnus was providing GNU support for the team, and 133was contracted to provide the required functionality. 134 135The name came from a conversation David Wallace was having with Richard 136Stallman about the library: RMS said that it would be quite hard---David 137said ``BFD''. Stallman was right, but the name stuck. 138 139At the same time, Ready Systems wanted much the same thing, but for 140different object file formats: IEEE-695, Oasys, Srecords, a.out and 68k 141coff. 142 143BFD was first implemented by members of Cygnus Support; Steve 144Chamberlain (@code{sac@@cygnus.com}), John Gilmore 145(@code{gnu@@cygnus.com}), K. Richard Pixley (@code{rich@@cygnus.com}) 146and David Henkel-Wallace (@code{gumby@@cygnus.com}). 147 148 149 150@node How It Works, What BFD Version 2 Can Do, History, Overview 151@section How To Use BFD 152 153To use the library, include @file{bfd.h} and link with @file{libbfd.a}. 154 155BFD provides a common interface to the parts of an object file 156for a calling application. 157 158When an application sucessfully opens a target file (object, archive, or 159whatever), a pointer to an internal structure is returned. This pointer 160points to a structure called @code{bfd}, described in 161@file{bfd.h}. Our convention is to call this pointer a BFD, and 162instances of it within code @code{abfd}. All operations on 163the target object file are applied as methods to the BFD. The mapping is 164defined within @code{bfd.h} in a set of macros, all beginning 165with @samp{bfd_} to reduce namespace pollution. 166 167For example, this sequence does what you would probably expect: 168return the number of sections in an object file attached to a BFD 169@code{abfd}. 170 171@lisp 172@c @cartouche 173#include "bfd.h" 174 175unsigned int number_of_sections(abfd) 176bfd *abfd; 177@{ 178 return bfd_count_sections(abfd); 179@} 180@c @end cartouche 181@end lisp 182 183The abstraction used within BFD is that an object file has: 184 185@itemize @bullet 186@item 187a header, 188@item 189a number of sections containing raw data (@pxref{Sections}), 190@item 191a set of relocations (@pxref{Relocations}), and 192@item 193some symbol information (@pxref{Symbols}). 194@end itemize 195@noindent 196Also, BFDs opened for archives have the additional attribute of an index 197and contain subordinate BFDs. This approach is fine for a.out and coff, 198but loses efficiency when applied to formats such as S-records and 199IEEE-695. 200 201@node What BFD Version 2 Can Do, , How It Works, Overview 202@section What BFD Version 2 Can Do 203@include bfdsumm.texi 204 205@node BFD front end, BFD back ends, Overview, Top 206@chapter BFD front end 207@include bfdt.texi 208 209@menu 210* Memory Usage:: 211* Initialization:: 212* Sections:: 213* Symbols:: 214* Archives:: 215* Formats:: 216* Relocations:: 217* Core Files:: 218* Targets:: 219* Architectures:: 220* Opening and Closing:: 221* Internal:: 222* File Caching:: 223* Linker Functions:: 224* Hash Tables:: 225@end menu 226 227@node Memory Usage, Initialization, BFD front end, BFD front end 228@section Memory usage 229BFD keeps all of its internal structures in obstacks. There is one obstack 230per open BFD file, into which the current state is stored. When a BFD is 231closed, the obstack is deleted, and so everything which has been 232allocated by BFD for the closing file is thrown away. 233 234BFD does not free anything created by an application, but pointers into 235@code{bfd} structures become invalid on a @code{bfd_close}; for example, 236after a @code{bfd_close} the vector passed to 237@code{bfd_canonicalize_symtab} is still around, since it has been 238allocated by the application, but the data that it pointed to are 239lost. 240 241The general rule is to not close a BFD until all operations dependent 242upon data from the BFD have been completed, or all the data from within 243the file has been copied. To help with the management of memory, there 244is a function (@code{bfd_alloc_size}) which returns the number of bytes 245in obstacks associated with the supplied BFD. This could be used to 246select the greediest open BFD, close it to reclaim the memory, perform 247some operation and reopen the BFD again, to get a fresh copy of the data 248structures. 249 250@node Initialization, Sections, Memory Usage, BFD front end 251@include init.texi 252 253@node Sections, Symbols, Initialization, BFD front end 254@include section.texi 255 256@node Symbols, Archives, Sections, BFD front end 257@include syms.texi 258 259@node Archives, Formats, Symbols, BFD front end 260@include archive.texi 261 262@node Formats, Relocations, Archives, BFD front end 263@include format.texi 264 265@node Relocations, Core Files, Formats, BFD front end 266@include reloc.texi 267 268@node Core Files, Targets, Relocations, BFD front end 269@include core.texi 270 271@node Targets, Architectures, Core Files, BFD front end 272@include targets.texi 273 274@node Architectures, Opening and Closing, Targets, BFD front end 275@include archures.texi 276 277@node Opening and Closing, Internal, Architectures, BFD front end 278@include opncls.texi 279 280@node Internal, File Caching, Opening and Closing, BFD front end 281@include libbfd.texi 282 283@node File Caching, Linker Functions, Internal, BFD front end 284@include cache.texi 285 286@node Linker Functions, Hash Tables, File Caching, BFD front end 287@include linker.texi 288 289@node Hash Tables, , Linker Functions, BFD front end 290@include hash.texi 291 292@node BFD back ends, GNU Free Documentation License, BFD front end, Top 293@chapter BFD back ends 294@menu 295* What to Put Where:: 296* aout :: a.out backends 297* coff :: coff backends 298* elf :: elf backends 299@ignore 300* oasys :: oasys backends 301* ieee :: ieee backend 302* srecord :: s-record backend 303@end ignore 304@end menu 305@node What to Put Where, aout, BFD back ends, BFD back ends 306All of BFD lives in one directory. 307 308@node aout, coff, What to Put Where, BFD back ends 309@include aoutx.texi 310 311@node coff, elf, aout, BFD back ends 312@include coffcode.texi 313 314@node elf, , coff, BFD back ends 315@include elf.texi 316@c Leave this out until the file has some actual contents... 317@c @include elfcode.texi 318 319@node GNU Free Documentation License, Index, BFD back ends, Top 320@chapter GNU Free Documentation License 321@cindex GNU Free Documentation License 322 323 GNU Free Documentation License 324 325 Version 1.1, March 2000 326 327 Copyright (C) 2000 Free Software Foundation, Inc. 328 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA 329 330 Everyone is permitted to copy and distribute verbatim copies 331 of this license document, but changing it is not allowed. 332 333 3340. PREAMBLE 335 336The purpose of this License is to make a manual, textbook, or other 337written document "free" in the sense of freedom: to assure everyone 338the effective freedom to copy and redistribute it, with or without 339modifying it, either commercially or noncommercially. Secondarily, 340this License preserves for the author and publisher a way to get 341credit for their work, while not being considered responsible for 342modifications made by others. 343 344This License is a kind of "copyleft", which means that derivative 345works of the document must themselves be free in the same sense. It 346complements the GNU General Public License, which is a copyleft 347license designed for free software. 348 349We have designed this License in order to use it for manuals for free 350software, because free software needs free documentation: a free 351program should come with manuals providing the same freedoms that the 352software does. But this License is not limited to software manuals; 353it can be used for any textual work, regardless of subject matter or 354whether it is published as a printed book. We recommend this License 355principally for works whose purpose is instruction or reference. 356 357 3581. APPLICABILITY AND DEFINITIONS 359 360This License applies to any manual or other work that contains a 361notice placed by the copyright holder saying it can be distributed 362under the terms of this License. The "Document", below, refers to any 363such manual or work. Any member of the public is a licensee, and is 364addressed as "you". 365 366A "Modified Version" of the Document means any work containing the 367Document or a portion of it, either copied verbatim, or with 368modifications and/or translated into another language. 369 370A "Secondary Section" is a named appendix or a front-matter section of 371the Document that deals exclusively with the relationship of the 372publishers or authors of the Document to the Document's overall subject 373(or to related matters) and contains nothing that could fall directly 374within that overall subject. (For example, if the Document is in part a 375textbook of mathematics, a Secondary Section may not explain any 376mathematics.) The relationship could be a matter of historical 377connection with the subject or with related matters, or of legal, 378commercial, philosophical, ethical or political position regarding 379them. 380 381The "Invariant Sections" are certain Secondary Sections whose titles 382are designated, as being those of Invariant Sections, in the notice 383that says that the Document is released under this License. 384 385The "Cover Texts" are certain short passages of text that are listed, 386as Front-Cover Texts or Back-Cover Texts, in the notice that says that 387the Document is released under this License. 388 389A "Transparent" copy of the Document means a machine-readable copy, 390represented in a format whose specification is available to the 391general public, whose contents can be viewed and edited directly and 392straightforwardly with generic text editors or (for images composed of 393pixels) generic paint programs or (for drawings) some widely available 394drawing editor, and that is suitable for input to text formatters or 395for automatic translation to a variety of formats suitable for input 396to text formatters. A copy made in an otherwise Transparent file 397format whose markup has been designed to thwart or discourage 398subsequent modification by readers is not Transparent. A copy that is 399not "Transparent" is called "Opaque". 400 401Examples of suitable formats for Transparent copies include plain 402ASCII without markup, Texinfo input format, LaTeX input format, SGML 403or XML using a publicly available DTD, and standard-conforming simple 404HTML designed for human modification. Opaque formats include 405PostScript, PDF, proprietary formats that can be read and edited only 406by proprietary word processors, SGML or XML for which the DTD and/or 407processing tools are not generally available, and the 408machine-generated HTML produced by some word processors for output 409purposes only. 410 411The "Title Page" means, for a printed book, the title page itself, 412plus such following pages as are needed to hold, legibly, the material 413this License requires to appear in the title page. For works in 414formats which do not have any title page as such, "Title Page" means 415the text near the most prominent appearance of the work's title, 416preceding the beginning of the body of the text. 417 418 4192. VERBATIM COPYING 420 421You may copy and distribute the Document in any medium, either 422commercially or noncommercially, provided that this License, the 423copyright notices, and the license notice saying this License applies 424to the Document are reproduced in all copies, and that you add no other 425conditions whatsoever to those of this License. You may not use 426technical measures to obstruct or control the reading or further 427copying of the copies you make or distribute. However, you may accept 428compensation in exchange for copies. If you distribute a large enough 429number of copies you must also follow the conditions in section 3. 430 431You may also lend copies, under the same conditions stated above, and 432you may publicly display copies. 433 434 4353. COPYING IN QUANTITY 436 437If you publish printed copies of the Document numbering more than 100, 438and the Document's license notice requires Cover Texts, you must enclose 439the copies in covers that carry, clearly and legibly, all these Cover 440Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on 441the back cover. Both covers must also clearly and legibly identify 442you as the publisher of these copies. The front cover must present 443the full title with all words of the title equally prominent and 444visible. You may add other material on the covers in addition. 445Copying with changes limited to the covers, as long as they preserve 446the title of the Document and satisfy these conditions, can be treated 447as verbatim copying in other respects. 448 449If the required texts for either cover are too voluminous to fit 450legibly, you should put the first ones listed (as many as fit 451reasonably) on the actual cover, and continue the rest onto adjacent 452pages. 453 454If you publish or distribute Opaque copies of the Document numbering 455more than 100, you must either include a machine-readable Transparent 456copy along with each Opaque copy, or state in or with each Opaque copy 457a publicly-accessible computer-network location containing a complete 458Transparent copy of the Document, free of added material, which the 459general network-using public has access to download anonymously at no 460charge using public-standard network protocols. If you use the latter 461option, you must take reasonably prudent steps, when you begin 462distribution of Opaque copies in quantity, to ensure that this 463Transparent copy will remain thus accessible at the stated location 464until at least one year after the last time you distribute an Opaque 465copy (directly or through your agents or retailers) of that edition to 466the public. 467 468It is requested, but not required, that you contact the authors of the 469Document well before redistributing any large number of copies, to give 470them a chance to provide you with an updated version of the Document. 471 472 4734. MODIFICATIONS 474 475You may copy and distribute a Modified Version of the Document under 476the conditions of sections 2 and 3 above, provided that you release 477the Modified Version under precisely this License, with the Modified 478Version filling the role of the Document, thus licensing distribution 479and modification of the Modified Version to whoever possesses a copy 480of it. In addition, you must do these things in the Modified Version: 481 482A. Use in the Title Page (and on the covers, if any) a title distinct 483 from that of the Document, and from those of previous versions 484 (which should, if there were any, be listed in the History section 485 of the Document). You may use the same title as a previous version 486 if the original publisher of that version gives permission. 487B. List on the Title Page, as authors, one or more persons or entities 488 responsible for authorship of the modifications in the Modified 489 Version, together with at least five of the principal authors of the 490 Document (all of its principal authors, if it has less than five). 491C. State on the Title page the name of the publisher of the 492 Modified Version, as the publisher. 493D. Preserve all the copyright notices of the Document. 494E. Add an appropriate copyright notice for your modifications 495 adjacent to the other copyright notices. 496F. Include, immediately after the copyright notices, a license notice 497 giving the public permission to use the Modified Version under the 498 terms of this License, in the form shown in the Addendum below. 499G. Preserve in that license notice the full lists of Invariant Sections 500 and required Cover Texts given in the Document's license notice. 501H. Include an unaltered copy of this License. 502I. Preserve the section entitled "History", and its title, and add to 503 it an item stating at least the title, year, new authors, and 504 publisher of the Modified Version as given on the Title Page. If 505 there is no section entitled "History" in the Document, create one 506 stating the title, year, authors, and publisher of the Document as 507 given on its Title Page, then add an item describing the Modified 508 Version as stated in the previous sentence. 509J. Preserve the network location, if any, given in the Document for 510 public access to a Transparent copy of the Document, and likewise 511 the network locations given in the Document for previous versions 512 it was based on. These may be placed in the "History" section. 513 You may omit a network location for a work that was published at 514 least four years before the Document itself, or if the original 515 publisher of the version it refers to gives permission. 516K. In any section entitled "Acknowledgements" or "Dedications", 517 preserve the section's title, and preserve in the section all the 518 substance and tone of each of the contributor acknowledgements 519 and/or dedications given therein. 520L. Preserve all the Invariant Sections of the Document, 521 unaltered in their text and in their titles. Section numbers 522 or the equivalent are not considered part of the section titles. 523M. Delete any section entitled "Endorsements". Such a section 524 may not be included in the Modified Version. 525N. Do not retitle any existing section as "Endorsements" 526 or to conflict in title with any Invariant Section. 527 528If the Modified Version includes new front-matter sections or 529appendices that qualify as Secondary Sections and contain no material 530copied from the Document, you may at your option designate some or all 531of these sections as invariant. To do this, add their titles to the 532list of Invariant Sections in the Modified Version's license notice. 533These titles must be distinct from any other section titles. 534 535You may add a section entitled "Endorsements", provided it contains 536nothing but endorsements of your Modified Version by various 537parties--for example, statements of peer review or that the text has 538been approved by an organization as the authoritative definition of a 539standard. 540 541You may add a passage of up to five words as a Front-Cover Text, and a 542passage of up to 25 words as a Back-Cover Text, to the end of the list 543of Cover Texts in the Modified Version. Only one passage of 544Front-Cover Text and one of Back-Cover Text may be added by (or 545through arrangements made by) any one entity. If the Document already 546includes a cover text for the same cover, previously added by you or 547by arrangement made by the same entity you are acting on behalf of, 548you may not add another; but you may replace the old one, on explicit 549permission from the previous publisher that added the old one. 550 551The author(s) and publisher(s) of the Document do not by this License 552give permission to use their names for publicity for or to assert or 553imply endorsement of any Modified Version. 554 555 5565. COMBINING DOCUMENTS 557 558You may combine the Document with other documents released under this 559License, under the terms defined in section 4 above for modified 560versions, provided that you include in the combination all of the 561Invariant Sections of all of the original documents, unmodified, and 562list them all as Invariant Sections of your combined work in its 563license notice. 564 565The combined work need only contain one copy of this License, and 566multiple identical Invariant Sections may be replaced with a single 567copy. If there are multiple Invariant Sections with the same name but 568different contents, make the title of each such section unique by 569adding at the end of it, in parentheses, the name of the original 570author or publisher of that section if known, or else a unique number. 571Make the same adjustment to the section titles in the list of 572Invariant Sections in the license notice of the combined work. 573 574In the combination, you must combine any sections entitled "History" 575in the various original documents, forming one section entitled 576"History"; likewise combine any sections entitled "Acknowledgements", 577and any sections entitled "Dedications". You must delete all sections 578entitled "Endorsements." 579 580 5816. COLLECTIONS OF DOCUMENTS 582 583You may make a collection consisting of the Document and other documents 584released under this License, and replace the individual copies of this 585License in the various documents with a single copy that is included in 586the collection, provided that you follow the rules of this License for 587verbatim copying of each of the documents in all other respects. 588 589You may extract a single document from such a collection, and distribute 590it individually under this License, provided you insert a copy of this 591License into the extracted document, and follow this License in all 592other respects regarding verbatim copying of that document. 593 594 5957. AGGREGATION WITH INDEPENDENT WORKS 596 597A compilation of the Document or its derivatives with other separate 598and independent documents or works, in or on a volume of a storage or 599distribution medium, does not as a whole count as a Modified Version 600of the Document, provided no compilation copyright is claimed for the 601compilation. Such a compilation is called an "aggregate", and this 602License does not apply to the other self-contained works thus compiled 603with the Document, on account of their being thus compiled, if they 604are not themselves derivative works of the Document. 605 606If the Cover Text requirement of section 3 is applicable to these 607copies of the Document, then if the Document is less than one quarter 608of the entire aggregate, the Document's Cover Texts may be placed on 609covers that surround only the Document within the aggregate. 610Otherwise they must appear on covers around the whole aggregate. 611 612 6138. TRANSLATION 614 615Translation is considered a kind of modification, so you may 616distribute translations of the Document under the terms of section 4. 617Replacing Invariant Sections with translations requires special 618permission from their copyright holders, but you may include 619translations of some or all Invariant Sections in addition to the 620original versions of these Invariant Sections. You may include a 621translation of this License provided that you also include the 622original English version of this License. In case of a disagreement 623between the translation and the original English version of this 624License, the original English version will prevail. 625 626 6279. TERMINATION 628 629You may not copy, modify, sublicense, or distribute the Document except 630as expressly provided for under this License. Any other attempt to 631copy, modify, sublicense or distribute the Document is void, and will 632automatically terminate your rights under this License. However, 633parties who have received copies, or rights, from you under this 634License will not have their licenses terminated so long as such 635parties remain in full compliance. 636 637 63810. FUTURE REVISIONS OF THIS LICENSE 639 640The Free Software Foundation may publish new, revised versions 641of the GNU Free Documentation License from time to time. Such new 642versions will be similar in spirit to the present version, but may 643differ in detail to address new problems or concerns. See 644http://www.gnu.org/copyleft/. 645 646Each version of the License is given a distinguishing version number. 647If the Document specifies that a particular numbered version of this 648License "or any later version" applies to it, you have the option of 649following the terms and conditions either of that specified version or 650of any later version that has been published (not as a draft) by the 651Free Software Foundation. If the Document does not specify a version 652number of this License, you may choose any version ever published (not 653as a draft) by the Free Software Foundation. 654 655 656ADDENDUM: How to use this License for your documents 657 658To use this License in a document you have written, include a copy of 659the License in the document and put the following copyright and 660license notices just after the title page: 661 662@smallexample 663 Copyright (c) YEAR YOUR NAME. 664 Permission is granted to copy, distribute and/or modify this document 665 under the terms of the GNU Free Documentation License, Version 1.1 666 or any later version published by the Free Software Foundation; 667 with the Invariant Sections being LIST THEIR TITLES, with the 668 Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. 669 A copy of the license is included in the section entitled "GNU 670 Free Documentation License". 671@end smallexample 672 673If you have no Invariant Sections, write "with no Invariant Sections" 674instead of saying which ones are invariant. If you have no 675Front-Cover Texts, write "no Front-Cover Texts" instead of 676"Front-Cover Texts being LIST"; likewise for Back-Cover Texts. 677 678If your document contains nontrivial examples of program code, we 679recommend releasing these examples in parallel under your choice of 680free software license, such as the GNU General Public License, 681to permit their use in free software. 682 683@node Index, , GNU Free Documentation License , Top 684@unnumbered Index 685@printindex cp 686 687@tex 688% I think something like @colophon should be in texinfo. In the 689% meantime: 690\long\def\colophon{\hbox to0pt{}\vfill 691\centerline{The body of this manual is set in} 692\centerline{\fontname\tenrm,} 693\centerline{with headings in {\bf\fontname\tenbf}} 694\centerline{and examples in {\tt\fontname\tentt}.} 695\centerline{{\it\fontname\tenit\/} and} 696\centerline{{\sl\fontname\tensl\/}} 697\centerline{are used for emphasis.}\vfill} 698\page\colophon 699% Blame: doc@cygnus.com, 28mar91. 700@end tex 701 702@contents 703@bye 704