From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
To: Newlib <newlib@sourceware.org>
Subject: Iconv.html and iconv.html
Date: Fri, 2 Dec 2022 17:06:03 +0100 [thread overview]
Message-ID: <419fd802-0895-3c9e-dd0d-be9963d7a83b@foss.st.com> (raw)
Hello,
I have been building a toolchain for the arm-none-eabi target using a
rather recent snapshot of newlib. While building the html documentation,
I noticed that there will be generated the two files named Iconv.html
and iconv.html.
While this works fine for case sensitive file systems, it's obvious that
this will not have the desired outcome on a case-insensitive file
system, such as on Windows system.
The Iconv.html file contains the chapter description and the iconv.html
file contains the description of the iconv-function.
Can someone, with the knowledge of how these filenames are generated,
change one of them so that the filenames differ on a case insensitive
file system?
Kind regards,
Torbjörn
next reply other threads:[~2022-12-02 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 16:06 Torbjorn SVENSSON [this message]
2022-12-09 16:29 ` Mike Frysinger
2022-12-09 16:40 ` Torbjorn SVENSSON
2022-12-10 8:29 ` Mike Frysinger
2022-12-10 8:29 ` [PATCH] newlib: info: tweak iconv node to avoid collisions Mike Frysinger
2022-12-13 1:28 ` Jeff Johnston
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=419fd802-0895-3c9e-dd0d-be9963d7a83b@foss.st.com \
--to=torbjorn.svensson@foss.st.com \
--cc=newlib@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).