From: Andrew Cagney <ac131313@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: [rfa/doc] tex -> texindex -> tex -> texindex -> tex
Date: Mon, 21 Jan 2002 00:35:00 -0000 [thread overview]
Message-ID: <3C4BD2CA.10407@cygnus.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
Hello,
Noticed that the texinfo 4.0 doco mentions that, when building
documentation, the sequence:
tex
texindex
tex
texindex
tex
should be used. The attached does this.
Ok?
Andrew
--
To summarize, this is a five step process:
1. Run `tex' on your Texinfo file. This generates a DVI file (with
undefined cross-references and no indices), and the raw index files
(with two letter extensions).
2. Run `texindex' on the raw index files. This creates the
corresponding sorted index files (with three letter extensions).
3. Run `tex' again on your Texinfo file. This regenerates the DVI
file, this time with indices and defined cross-references, but
with page numbers for the cross-references from last time,
generally incorrect.
4. Sort the indices again, with `texindex'.
5. Run `tex' one last time. This time the correct page numbers are
written for the cross-references.
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1754 bytes --]
2002-01-21 Andrew Cagney <ac131313@redhat.com>
* Makefile.in: Update copyright.
(gdb.dvi, gdb.pdf, gdbint.dvi, gdbint.pdf): Use the sequence tex,
texindex, tex, texindex, tex, when generating documents.
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/doc/Makefile.in,v
retrieving revision 1.17
diff -u -r1.17 Makefile.in
--- Makefile.in 2002/01/17 08:54:12 1.17
+++ Makefile.in 2002/01/21 08:28:53
@@ -1,4 +1,4 @@
-##Copyright 1991, 1992, 1993, 1994, 1995, 1996, 1999, 2000
+##Copyright 1991, 1992, 1993, 1994, 1995, 1996, 1999, 2000, 2002
##Free Software Foundation, Inc.
# Makefile for GDB documentation.
@@ -247,6 +247,7 @@
ln $(srcdir)/GDBvn.texi . || \
cp $(srcdir)/GDBvn.texi . ; else true; fi
$(SET_TEXINPUTS) $(TEX) gdb.texinfo
+ $(TEXINDEX) gdb.??
$(SET_TEXINPUTS) $(TEX) gdb.texinfo
$(TEXINDEX) gdb.??
$(SET_TEXINPUTS) $(TEX) gdb.texinfo
@@ -262,6 +263,7 @@
ln $(srcdir)/GDBvn.texi . || \
cp $(srcdir)/GDBvn.texi . ; else true; fi
$(SET_TEXINPUTS) $(PDFTEX) gdb.texinfo
+ $(TEXINDEX) gdb.??
$(SET_TEXINPUTS) $(PDFTEX) gdb.texinfo
$(TEXINDEX) gdb.??
$(SET_TEXINPUTS) $(PDFTEX) gdb.texinfo
@@ -375,6 +377,8 @@
$(SET_TEXINPUTS) $(TEX) gdbint.texinfo
$(TEXINDEX) gdbint.??
$(SET_TEXINPUTS) $(TEX) gdbint.texinfo
+ $(TEXINDEX) gdbint.??
+ $(SET_TEXINPUTS) $(TEX) gdbint.texinfo
rm -f gdbint.aux gdbint.cp* gdbint.fn* gdbint.ky* \
gdbint.log gdbint.pg* gdbint.toc gdbint.tp* gdbint.vr*
@@ -382,6 +386,8 @@
$(DVIPS) -o $@ $?
gdbint.pdf: gdbint.dvi
+ $(SET_TEXINPUTS) $(PDFTEX) gdbint.texinfo
+ $(TEXINDEX) gdbint.??
$(SET_TEXINPUTS) $(PDFTEX) gdbint.texinfo
$(TEXINDEX) gdbint.??
$(SET_TEXINPUTS) $(PDFTEX) gdbint.texinfo
next reply other threads:[~2002-01-21 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 0:35 Andrew Cagney [this message]
2002-01-21 2:23 ` Eli Zaretskii
2002-01-21 10:59 ` Andrew Cagney
2002-01-21 14:51 ` Andrew Cagney
2002-01-22 0:59 ` Eli Zaretskii
2002-01-22 8:37 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C4BD2CA.10407@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox