From: Eli Zaretskii <eliz@gnu.org>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Fix doc index name on Windows
Date: Fri, 26 Nov 2010 11:55:00 -0000 [thread overview]
Message-ID: <83ipzk70w4.fsf@gnu.org> (raw)
In-Reply-To: <4CEEAF36.7030005@eCosCentric.com>
> Date: Thu, 25 Nov 2010 18:47:18 +0000
> From: Jonathan Larmour <jifl@eCosCentric.com>
> CC: gdb-patches@sourceware.org
>
> On 25/11/10 18:23, Eli Zaretskii wrote:
> >> Date: Thu, 25 Nov 2010 17:40:07 +0000
> >> From: Jonathan Larmour <jifl@eCosCentric.com>
> >>
> >> 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.
> >
> > What version of Texinfo is that?
>
> The tools I build are generated on a RHEL4 machine, which is therefore a
> bit on the older side intentionally for wider binary compatibility
> (although that doesn't affect docs, true). It's texinfo 4.7.
Then it's a bug in the cross-build version of makeinfo. There's code
in makeinfo/node.c:cm_node to handle the case when a file name
produced from a node name clashes with a name of an existing file
(produced from some other node name), due to limitations of the
underlying filesystem. What makeinfo does in that case is put all the
nodes whose names map to the same file name on that single file. I
see this behavior in action in the Windows port of makeinfo 4.8, and
the code which does this was written long before Texinfo 4.7 was
released, so you must have it as well.
I guess whoever produced the cross-build environment didn't make sure
this feature is turned on, even though the RHEL4 filesystem does not
need this.
I don't like the name you suggest, "GDB Index". That chapter is not
an index of GDB, it's an index of a manual. I can go with something
like "Concept and Command Index" instead (and will accept such a patch
if you insist on fixing this in GDB), but I really think you should
take care of this in your cross-build environment, because that's
where the bug is.
Thanks.
next prev parent reply other threads:[~2010-11-26 11:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 17:40 Jonathan Larmour
2010-11-25 18:21 ` Eli Zaretskii
2010-11-25 18:47 ` Jonathan Larmour
2010-11-26 11:55 ` Eli Zaretskii [this message]
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=83ipzk70w4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jifl@eCosCentric.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