From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id FRFmLYa5u2N3xhIAWB0awg (envelope-from ) for ; Mon, 09 Jan 2023 01:51:50 -0500 Received: by simark.ca (Postfix, from userid 112) id AC59D1E222; Mon, 9 Jan 2023 01:51:50 -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=CargnVoK; 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=-9.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_HI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.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 64CBD1E110 for ; Mon, 9 Jan 2023 01:51:50 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id D1F773858C2D for ; Mon, 9 Jan 2023 06:51:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D1F773858C2D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1673247109; bh=qdDvcVUtO1LmRh1UHv1BFXlwnn4/BYzUDt8ey2/lIX0=; 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=CargnVoK9v4pSPMmHhVtuNSGizzxT4Srt0J+WCyLu0x5GfObUXj9heiQ644UJfH01 hTWDEKkiVxoTpI6vrRkwZ9btNr2ogorPGHIkTp7XB+T7apdJ1sP0vINi7zhIarxodc DC5kVKMWkERdM7nzLHqqKe2qvKoZFAvLv3QF+E7U= Received: from mx07-00178001.pphosted.com (mx08-00178001.pphosted.com [91.207.212.93]) by sourceware.org (Postfix) with ESMTPS id 135AA3858D33 for ; Mon, 9 Jan 2023 06:51:29 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 135AA3858D33 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 3091i7oY029382; Mon, 9 Jan 2023 07:51:20 +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 3my0gnqy31-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 09 Jan 2023 07:51:20 +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 7E76D10003A; Mon, 9 Jan 2023 07:51:18 +0100 (CET) Received: from Webmail-eu.st.com (shfdag1node3.st.com [10.75.129.71]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id 8200220FE2C; Mon, 9 Jan 2023 07:51:18 +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; Mon, 9 Jan 2023 07:51:18 +0100 Message-ID: <64679b6c-e318-0b7a-2dad-9a1f716f9ba8@foss.st.com> Date: Mon, 9 Jan 2023 07:51:17 +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> <778ba370-2304-bc7f-c160-9adb24c05f9b@foss.st.com> <83y1qesjys.fsf@gnu.org> <83sfgmsit3.fsf@gnu.org> In-Reply-To: <83sfgmsit3.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-09_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 12:08, Eli Zaretskii wrote: >> Date: Sat, 7 Jan 2023 11:52:45 +0100 >> CC: >> From: Torbjorn SVENSSON >> >> On 2023-01-07 11:43, Eli Zaretskii wrote: >>>> Date: Sat, 7 Jan 2023 10:42:11 +0100 >>>> CC: >>>> From: Torbjorn SVENSSON >>>> >>>> Do you see any use of the ~214 redirect pages in the GDB context? >>> >>> Sorry, I don't understand the question. What do you mean by "see any >>> use" in this context? >> >> I was considering if the redirect files could simply be removed from the >> GDB documentation tree or if they are actually used for inter components >> references. > > They are produced by makeinfo, and they are produced for a reason, no? According to the other thread, they are generated to easy cross linking the documentation. There is nothing in the documentation that will generate a link to any of these files, so hence the question if they are needed by GDB. > >> I'm more or less trying to find the best solution for GDB. >> >> There is the possibility to rename one of the [qQ]MemTags anchors in the >> GDB documentation, but that will also include the alternative name in >> the redirect page and it would require all the @xref etc to be updated >> to the renamed anchor. >> >> Even if we get a solution merged in texinfo, it will take years for it >> to get activity used, and in the mean while, we are stuck with this >> issue in GDB. > > I still don't want to make any conclusions until the Texinfo > discussion is completed. How do you know there's no solution with the > existing Texinfo versions? As I understood it, it was proved that the redirect pages were colliding and no way around that in current implementation, but maybe I misunderstood the reply...