From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Doc fixes for makeinfo --html
Date: Wed, 14 Jan 2009 11:31:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0901141121250.9454@digraph.polyomino.org.uk> (raw)
In-Reply-To: <uk58ybjmr.fsf@gnu.org>
On Wed, 14 Jan 2009, Eli Zaretskii wrote:
> > * To work on case-insensitive filesystems with makeinfo splitting by
> > node, the index should not be called "Index" as this clashes with
> > the automatically generated index.html.
>
> In what version of makeinfo did you see this problem, and on what OS
> and which port? Because it was solved long ago: when some <node>.html
> clashes with another <node>.html, makeinfo should resolve the clash
> automatically.
Various versions of makeinfo up to 4.12. The problem is building GDB on
i686-pc-linux-gnu (build system) with --host=i686-mingw32; I have not
tried any version of makeinfo running directly on the case-insensitive
systems (we build all tools for all hosts on GNU/Linux build systems).
There is no way to pass the expected host to makeinfo, and since
documentation goes in a "share" directory the files generated should not
depend at all on the host in any case; it would be a bug for the files in
the share directory to differ for different --host configurations.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2009-01-14 11:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 2:51 Joseph S. Myers
2009-01-14 4:24 ` Eli Zaretskii
2009-01-14 11:31 ` Joseph S. Myers [this message]
2009-01-14 11:54 ` Joseph S. Myers
2009-01-14 19:22 ` 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=Pine.LNX.4.64.0901141121250.9454@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=eliz@gnu.org \
--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