From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id QhQLIJc+uWNYhhEAWB0awg (envelope-from ) for ; Sat, 07 Jan 2023 04:42:47 -0500 Received: by simark.ca (Postfix, from userid 112) id 76C191E222; Sat, 7 Jan 2023 04:42:47 -0500 (EST) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=xdtZ0Wc5; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-8.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_HI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 7EB7B1E0D3 for ; Sat, 7 Jan 2023 04:42:46 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id A21833858CDB for ; Sat, 7 Jan 2023 09:42:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A21833858CDB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1673084564; bh=6eKVnwMGEKK5FB2ERNcpMuX9MyeuXxPOChrVIWhGBEE=; h=Date:Subject:To:CC:References:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=xdtZ0Wc5m0S2w1+I1jqhUgheEHsG+E84Pz0OOPs0g+VAq1u/lubp+SRsKxsZDCg/+ BnmTbAeYhPbEfyKrRar6C6d4AuaFmJWn7KcgrA/E81HRlgxIZ9Yw8Xd2bqRwbl0RPU y3cK5xdn7qzpPsHDJ2pyZPLkjfbrkr+X73+TF9Fc= Received: from mx07-00178001.pphosted.com (mx08-00178001.pphosted.com [91.207.212.93]) by sourceware.org (Postfix) with ESMTPS id 7683C3858D39 for ; Sat, 7 Jan 2023 09:42:24 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 7683C3858D39 Received: from pps.filterd (m0046661.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 307346Jj008613; Sat, 7 Jan 2023 10:42:16 +0100 Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx07-00178001.pphosted.com (PPS) with ESMTPS id 3my0gnh29n-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 07 Jan 2023 10:42:16 +0100 Received: from euls16034.sgp.st.com (euls16034.sgp.st.com [10.75.44.20]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 0A9C6100034; Sat, 7 Jan 2023 10:42:15 +0100 (CET) Received: from Webmail-eu.st.com (shfdag1node3.st.com [10.75.129.71]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id 12EB6237D8D; Sat, 7 Jan 2023 10:42:15 +0100 (CET) Received: from [10.252.8.65] (10.252.8.65) by SHFDAG1NODE3.st.com (10.75.129.71) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.13; Sat, 7 Jan 2023 10:42:12 +0100 Message-ID: <778ba370-2304-bc7f-c160-9adb24c05f9b@foss.st.com> Date: Sat, 7 Jan 2023 10:42:11 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: Generated GDB documentation have colliding files on a case insensitive files system Content-Language: en-US To: Eli Zaretskii CC: References: <831qo6u1m0.fsf@gnu.org> In-Reply-To: <831qo6u1m0.fsf@gnu.org> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.252.8.65] X-ClientProxiedBy: SHFCAS1NODE1.st.com (10.75.129.72) To SHFDAG1NODE3.st.com (10.75.129.71) X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.923,Hydra:6.0.545,FMLib:17.11.122.1 definitions=2023-01-07_02,2023-01-06_01,2022-06-22_01 X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Torbjorn SVENSSON via Gdb-patches Reply-To: Torbjorn SVENSSON Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 2023-01-07 10:37, Eli Zaretskii wrote: >> Date: Sat, 7 Jan 2023 10:21:49 +0100 >> From: Torbjorn SVENSSON >> CC: Eli Zaretskii >> >> If the HTML documentation is put on a case insensitive files system >> (like those used in Windows), there are 2 files that collides: >> qMemTags.html and QMemTags.html. >> >> Both the files contains a simple redirect to their corresponding anchor >> in General-Query-Packets.html, and there appears to be no link to >> [qQ]MemTags.html in any of the other generated HTML files. >> I'm currently leaning towards that these redirect files are not really >> needed and that they should have been omitted. >> >> As it's correct to document both qMemTags and QMemTags, and that the two >> RSP commands are indeed different, I see the following potential >> solutions to the collision: >> >> * Leave it as is and live with the collision for users extracting an >> archive with the HTML documentation on a case insensitive files system. >> >> * Use the "--no-split" argument to makeinfo to generate a single big >> HTML file for all the documentation rather than one HTML file per @node. >> This solution might have other consequences that I'm not aware of as >> there are multiple texi files in the GDB source tree... >> >> * After invoking makeinfo, remove all the generated redirect pages >> (appears to be ~214 files). >> >> >> Is there any other solution that I have no thought of? > > Yes, there are other solutions. For example, one of the files could > have been renamed to a different name, when the collision is detected. > > FWIW, the old makeinfo 4.x did succeed to avoid file-name conflicts in > this and other similar cases. That solution it used was lost when > makeinfo was reimplemented in Perl, and AFAIU it cannot be easily > adopted by the current makeinfo implementation, because it changed the > way nodes are references in the " >> I've also started a thread on the bug-texinfo list about adding a >> warning for this problem when running the makeinfo command. The thread >> can be found here: >> https://lists.gnu.org/archive/html/bug-texinfo/2023-01/msg00030.html > > Let's wait for that other discussion to conclude, and then take it > from there. I'd prefer a solution in Texinfo rather than in GDB, as > this is a general problem. I agree.