From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx07-00178001.pphosted.com (mx08-00178001.pphosted.com [91.207.212.93]) by sourceware.org (Postfix) with ESMTPS id 569503858D32 for ; Sun, 15 Jan 2023 17:44:04 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 569503858D32 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=foss.st.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=foss.st.com Received: from pps.filterd (m0046660.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 30FGRwDD003952; Sun, 15 Jan 2023 18:43:58 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foss.st.com; h=message-id : date : mime-version : subject : to : cc : references : from : in-reply-to : content-type : content-transfer-encoding; s=selector1; bh=NImsmwXExHFIvD9jvXBKJCklhMRUSctqh3E+7N+YJeU=; b=EGS81uFI7Nz3J4sqM6N5pQeaI55UqS+ElOmPBuuIavcwGOdNRhfqIM66i9fr8mnUCuT+ 279lfUht/XhJXWE9GnoSEvQvyYjaYW7zM5skLqnIDCYgPosvojAG171WVpdFIMGEBqlZ jccBfA4pW/s4haa3/2Y1AkrRKntYMmCtcB9mni8gde+OV/5vcE7zou/AtP4fFYcr1r5S ElXkMCqQvcTvQkZJTByctY3E5a+aFwcIA8YfeRR0MBsQewMcLG0pgnWZIjKRxpVuALF8 9CQas3qGdEepDpYSY6gC7Nfpq+kCLDojkqUQlojebawKknKZB1dfjVnDtkJENnYxv+gB FQ== 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 3n3jdewt6h-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 15 Jan 2023 18:43:58 +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 4668B10002A; Sun, 15 Jan 2023 18:43:57 +0100 (CET) Received: from Webmail-eu.st.com (shfdag1node3.st.com [10.75.129.71]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id 28F1621ADDE; Sun, 15 Jan 2023 18:43:57 +0100 (CET) Received: from [10.252.29.48] (10.252.29.48) 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; Sun, 15 Jan 2023 18:43:54 +0100 Message-ID: <1b42d7a8-801b-941c-998b-2f11a11bbe2d@foss.st.com> Date: Sun, 15 Jan 2023 18:43:53 +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> <64679b6c-e318-0b7a-2dad-9a1f716f9ba8@foss.st.com> <83a62rq4jg.fsf@gnu.org> <837cxn66k8.fsf@gnu.org> From: Torbjorn SVENSSON In-Reply-To: <837cxn66k8.fsf@gnu.org> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.252.29.48] 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.219,Aquarius:18.0.923,Hydra:6.0.562,FMLib:17.11.122.1 definitions=2023-01-15_13,2023-01-13_02,2022-06-22_01 X-Spam-Status: No, score=-5.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,NICE_REPLY_A,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 2023-01-15 18:39, Eli Zaretskii wrote: >> Date: Sun, 15 Jan 2023 18:22:54 +0100 >> CC: >> From: Torbjorn SVENSSON >> >> 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? I suppose that would work, but there would be no indication of a potential future clash. Maybe that's okay anyway?