From: Eli Zaretskii <eliz@gnu.org>
To: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Generated GDB documentation have colliding files on a case insensitive files system
Date: Sun, 15 Jan 2023 19:39:19 +0200 [thread overview]
Message-ID: <837cxn66k8.fsf@gnu.org> (raw)
In-Reply-To: <a141b9c6-2a84-47ac-da44-1dfd380a39eb@foss.st.com> (message from Torbjorn SVENSSON on Sun, 15 Jan 2023 18:22:54 +0100)
> Date: Sun, 15 Jan 2023 18:22:54 +0100
> CC: <gdb-patches@sourceware.org>
> From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
>
> As I see it, there are 3 different options for the documentation in GDB:
>
> 1. Leave everything as is and forget about all users extracting a cross
> built GDB with documentation and let the users deal with duplicated files...
>
> 2. Set the CASE_INSENSITIVE_FILENAMES option and also change one of the
> anchors to have unique files. This will require Texinfo >7.0.1 that is
> not yet released.
>
> 3. Generate one single big HTML file. This should be supported with
> existing versions of Texinfo, although I haven't tested this option.
> What would be needed in GDB sources is to replace the command line
> option --split-size with --no-split to avoid generating more than one file.
>
>
> What option would you prefer?
I think we should rename one of the anchors, and otherwise leave
things at that, because doing so will resolve the problem even without
using CASE_INSENSITIVE_FILENAMES and without waiting for a future
release of Texinfo, right?
next prev parent reply other threads:[~2023-01-15 17:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 9:21 Torbjorn SVENSSON
2023-01-07 9:37 ` Eli Zaretskii
2023-01-07 9:42 ` Torbjorn SVENSSON
2023-01-07 10:43 ` Eli Zaretskii
2023-01-07 10:52 ` Torbjorn SVENSSON
2023-01-07 11:08 ` Eli Zaretskii
2023-01-09 6:51 ` Torbjorn SVENSSON
2023-01-09 12:24 ` Eli Zaretskii
2023-01-15 17:22 ` Torbjorn SVENSSON
2023-01-15 17:39 ` Eli Zaretskii [this message]
2023-01-15 17:43 ` Torbjorn SVENSSON
2023-01-15 18:09 ` 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=837cxn66k8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=torbjorn.svensson@foss.st.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).