This reverts commit
8bb23cdbb498ff645bb0937bc8c0cb89e9e5ebd8.
My earlier patch to simplifify the @node uses in the BFD manual didn't
take into account (1) that BFD doesn't use the ordinary texinfo
sectioning commands, and (2) that some users are stuck on very ancient
versions of makeinfo.
This patch reverts the change.
I went through the entire manual using the spacebar, trying to find
the original problem I reported in the change, but couldn't. I don't
know why. Anyway, all this means is that, with this reversion,
editing the node structure will be slightly less convenient.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30703
2023-08-30 Tom Tromey <tom@tromey.com>
PR binutils/30703
* doc/webassembly.texi, doc/bfd.texi: Revert
8bb23cdb, adding
parameters back to @node.
+2023-08-30 Tom Tromey <tom@tromey.com>
+
+ PR binutils/30703
+ * doc/webassembly.texi, doc/bfd.texi: Revert 8bb23cdb, adding
+ parameters back to @node.
+
2023-08-04 Nick Clifton <nickc@redhat.com>
PR 15545
2023-08-04 Nick Clifton <nickc@redhat.com>
PR 15545
+@node Top, Overview, (dir), (dir)
@ifinfo
This file documents the binary file descriptor library libbfd.
@end ifinfo
@ifinfo
This file documents the binary file descriptor library libbfd.
@end ifinfo
* BFD Index:: BFD Index
@end menu
* BFD Index:: BFD Index
@end menu
+@node Overview, BFD front end, Top, Top
@chapter Introduction
@cindex BFD
@cindex what is it?
@chapter Introduction
@cindex BFD
@cindex what is it?
* What BFD Version 2 Can Do:: What BFD Version 2 Can Do
@end menu
* What BFD Version 2 Can Do:: What BFD Version 2 Can Do
@end menu
+@node History, How It Works, Overview, Overview
@section History
One spur behind BFD was the desire, on the part of the GNU 960 team at
@section History
One spur behind BFD was the desire, on the part of the GNU 960 team at
+@node How It Works, What BFD Version 2 Can Do, History, Overview
@section How To Use BFD
To use the library, include @file{bfd.h} and link with @file{libbfd.a}.
@section How To Use BFD
To use the library, include @file{bfd.h} and link with @file{libbfd.a}.
but loses efficiency when applied to formats such as S-records and
IEEE-695.
but loses efficiency when applied to formats such as S-records and
IEEE-695.
-@node What BFD Version 2 Can Do
+@node What BFD Version 2 Can Do, , How It Works, Overview
@section What BFD Version 2 Can Do
@include bfdsumm.texi
@section What BFD Version 2 Can Do
@include bfdsumm.texi
+@node BFD front end, BFD back ends, Overview, Top
@chapter BFD Front End
@menu
@chapter BFD Front End
@menu
@include bfdt.texi
@include bfdio.texi
@include bfdt.texi
@include bfdio.texi
+@node Memory Usage, Sections, Miscellaneous, BFD front end
@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
@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
some operation and reopen the BFD again, to get a fresh copy of the data
structures.
some operation and reopen the BFD again, to get a fresh copy of the data
structures.
+@node Sections, Symbols, Memory Usage, BFD front end
+@node Symbols, Archives, Sections, BFD front end
+@node Archives, Formats, Symbols, BFD front end
+@node Formats, Relocations, Archives, BFD front end
+@node Relocations, Core Files, Formats, BFD front end
+@node Core Files, Targets, Relocations, BFD front end
+@node Targets, Architectures, Core Files, BFD front end
+@node Architectures, Opening and Closing, Targets, BFD front end
-@node Opening and Closing
+@node Opening and Closing, Internal, Architectures, BFD front end
+@node Internal, File Caching, Opening and Closing, BFD front end
+@node File Caching, Linker Functions, Internal, BFD front end
+@node Linker Functions, Hash Tables, File Caching, BFD front end
+@node Hash Tables, , Linker Functions, BFD front end
+@node BFD back ends, GNU Free Documentation License, BFD front end, Top
@chapter BFD back ends
@menu
* What to Put Where::
@chapter BFD back ends
@menu
* What to Put Where::
* srecord :: s-record backend
@end ignore
@end menu
* srecord :: s-record backend
@end ignore
@end menu
+@node What to Put Where, aout, BFD back ends, BFD back ends
@section What to Put Where
All of BFD lives in one directory.
@section What to Put Where
All of BFD lives in one directory.
+@node aout, coff, What to Put Where, BFD back ends
+@node coff, elf, aout, BFD back ends
+@node elf, mmo, coff, BFD back ends
@include elf.texi
@c Leave this out until the file has some actual contents...
@c @include elfcode.texi
@include elf.texi
@c Leave this out until the file has some actual contents...
@c @include elfcode.texi
+@node mmo, , elf, BFD back ends
-@node GNU Free Documentation License
+@node GNU Free Documentation License, BFD Index, BFD back ends, Top
+@node BFD Index, , GNU Free Documentation License, Top
@unnumbered BFD Index
@printindex cp
@unnumbered BFD Index
@printindex cp
* File layout::
@end menu
* File layout::
@end menu
+@node File layout, WebAssembly
@subsection File layout
For a description of the WebAssembly file format, see
@url{https://github.com/WebAssembly/design/blob/master/BinaryEncoding.md}.
@subsection File layout
For a description of the WebAssembly file format, see
@url{https://github.com/WebAssembly/design/blob/master/BinaryEncoding.md}.