From: Jonathan Larmour <jifl@eCosCentric.com>
To: gdb-patches@sourceware.org
Subject: Fix doc index name on Windows
Date: Thu, 25 Nov 2010 17:40:00 -0000 [thread overview]
Message-ID: <4CEE9F77.1070509@eCosCentric.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
When cross building GDB 7.2 to Windows I have found that the GDB
documentation set generates HTML files named index.html and Index.html. On
Windows this unfortunately doesn't work as those names match each other.
The former is the front page and ToC, the latter is the genuine Index at
the end of the documentation.
The simplest solution is just to rename the Index at the end to have a
different node name. This is what other GNU documentation sets (GAS, BFD,
CPP, etc.) do. So that's what the attached patch (against current CVS) does.
I have a copyright assignment and check-in permissions. Okay to commit?
2010-11-25 Jonathan Larmour <jifl@eCosCentric.com>
* gdb.texinfo (Top): Rename Index to GDB Index to prevent clashes
on Windows systems.
(Help): Likewise.
(Index): Likewise.
* gdbint.texinfo (Top): Similar but with Index to GDB Internals Index.
(GDB Internals Index): Likewise.
Jifl
--
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------ Opinions==mine
[-- Attachment #2: gdbdocidx.patch.txt --]
[-- Type: text/plain, Size: 2522 bytes --]
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.776
diff -u -5 -p -r1.776 gdb.texinfo
--- gdb.texinfo 23 Nov 2010 14:39:16 -0000 1.776
+++ gdb.texinfo 25 Nov 2010 17:33:49 -0000
@@ -182,11 +182,11 @@ software in general. We will miss him.
the operating system
* Trace File Format:: GDB trace file format
* Copying:: GNU General Public License says
how you can copy and share GDB
* GNU Free Documentation License:: The license for this documentation
-* Index:: Index
+* GDB Index:: Index
@end menu
@end ifnottex
@contents
@@ -1714,11 +1714,11 @@ inspect
In addition to @code{help}, you can use the @value{GDBN} commands @code{info}
and @code{show} to inquire about the state of your program, or the state
of @value{GDBN} itself. Each command supports many topics of inquiry; this
manual introduces each of them in the appropriate context. The listings
under @code{info} and under @code{show} in the Index point to
-all the sub-commands. @xref{Index}.
+all the sub-commands. @xref{GDB Index}.
@c @group
@table @code
@kindex info
@kindex i @r{(@code{info})}
@@ -36355,12 +36355,12 @@ which @value{GDBN} currently ignores.
@node GNU Free Documentation License
@appendix GNU Free Documentation License
@include fdl.texi
-@node Index
-@unnumbered Index
+@node GDB Index
+@unnumbered GDB Index
@printindex cp
@tex
% I think something like @colophon should be in texinfo. In the
Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.327
diff -u -5 -p -r1.327 gdbint.texinfo
--- gdbint.texinfo 20 Oct 2010 22:53:36 -0000 1.327
+++ gdbint.texinfo 25 Nov 2010 17:33:50 -0000
@@ -92,11 +92,11 @@ as the mechanisms that adapt @value{GDBN
* Testsuite::
* Hints::
* GDB Observers:: @value{GDBN} Currently available observers
* GNU Free Documentation License:: The license for this documentation
-* Index::
+* GDB Internals Index::
@end menu
@node Summary
@chapter Summary
@@ -8030,11 +8030,11 @@ in the directory the script was called f
@node GNU Free Documentation License
@appendix GNU Free Documentation License
@include fdl.texi
-@node Index
-@unnumbered Index
+@node GDB Internals Index
+@unnumbered GDB Internals Index
@printindex cp
@bye
next reply other threads:[~2010-11-25 17:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 17:40 Jonathan Larmour [this message]
2010-11-25 18:21 ` Eli Zaretskii
2010-11-25 18:47 ` Jonathan Larmour
2010-11-26 11:55 ` Eli Zaretskii
2010-11-26 12:03 ` Pedro Alves
2010-11-26 12:52 ` Eli Zaretskii
2010-11-26 13:05 ` Pedro Alves
2010-11-26 15:07 ` Jonathan Larmour
2010-11-26 16:15 ` Eli Zaretskii
2010-11-27 9:24 ` Andreas Schwab
2010-11-26 15:12 ` Jonathan Larmour
2010-11-26 16:08 ` Eli Zaretskii
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=4CEE9F77.1070509@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=gdb-patches@sourceware.org \
/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