From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id ood4Cl09uWOzhBEAWB0awg (envelope-from ) for ; Sat, 07 Jan 2023 04:37:33 -0500 Received: by simark.ca (Postfix, from userid 112) id 1ED011E222; Sat, 7 Jan 2023 04:37:33 -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=pYc/Xy8F; 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=-7.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,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 5AA1C1E0D3 for ; Sat, 7 Jan 2023 04:37:31 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 5B3743858C53 for ; Sat, 7 Jan 2023 09:37:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5B3743858C53 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1673084248; bh=b4RWuTRzrIosvhAUMrjx3Vm+GsIaELqebiuZ1Dnt0o0=; h=Date:To:Cc:In-Reply-To:Subject:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=pYc/Xy8FV+jd7iG9PfUa7He33Yi9OMBLvtWLffGFowHKE4tPGHIdfLaNCamAu+W1k TiOPXyO/K3uLWeuP/Om1BnALTmc/8GZUonYUaarkChRMi5eXKKOXYB2ICCNtCEVOt1 zV4Hx4wLxEjoHhgYaR7zqhvVxHxHsS1EAhk3n0m8= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 0B7973858D39 for ; Sat, 7 Jan 2023 09:37:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0B7973858D39 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pE5dT-0007x6-LA; Sat, 07 Jan 2023 04:37:07 -0500 Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pE5dS-0005Q1-RI; Sat, 07 Jan 2023 04:37:07 -0500 Date: Sat, 07 Jan 2023 11:37:27 +0200 Message-Id: <831qo6u1m0.fsf@gnu.org> To: Torbjorn SVENSSON Cc: gdb-patches@sourceware.org In-Reply-To: (message from Torbjorn SVENSSON on Sat, 7 Jan 2023 10:21:49 +0100) Subject: Re: Generated GDB documentation have colliding files on a case insensitive files system References: 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: Eli Zaretskii via Gdb-patches Reply-To: Eli Zaretskii Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" > 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.