From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 36MCKX5BxGPrqxcAWB0awg (envelope-from ) for ; Sun, 15 Jan 2023 13:10:06 -0500 Received: by simark.ca (Postfix, from userid 112) id 9DCFC1E128; Sun, 15 Jan 2023 13:10:06 -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=fQfZbkuy; 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=-5.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, 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 45DC31E0D3 for ; Sun, 15 Jan 2023 13:10:06 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 0FFAB3858C52 for ; Sun, 15 Jan 2023 18:10:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0FFAB3858C52 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1673806200; bh=irJWiuUVAcWAr9amTGvHx0xq5Mf5km85j63/+gGPN00=; 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=fQfZbkuyCuWe1P1mQnsfVm+IYUDLhRivbvHEdWBEgCWJv9zSaUjsc+D7zOImw3EdM atXVHRLy5JH+PppNlxOpEzhq0QZ8wS7NnTphTqdWmlJ+THtRl16tKM9t3mxBmD4Qxx gNstEtzEMd7wIGHjnA85XkhN2hu476Y6BjbUwLxs= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 26C823858D32 for ; Sun, 15 Jan 2023 18:09:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 26C823858D32 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 1pH7Rm-0003GT-A4; Sun, 15 Jan 2023 13:09:34 -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 1pH7Rl-0006RS-NB; Sun, 15 Jan 2023 13:09:34 -0500 Date: Sun, 15 Jan 2023 20:09:38 +0200 Message-Id: <835yd7655p.fsf@gnu.org> To: Torbjorn SVENSSON Cc: gdb-patches@sourceware.org In-Reply-To: <1b42d7a8-801b-941c-998b-2f11a11bbe2d@foss.st.com> (message from Torbjorn SVENSSON on Sun, 15 Jan 2023 18:43:53 +0100) Subject: Re: Generated GDB documentation have colliding files on a case insensitive files system 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> <1b42d7a8-801b-941c-998b-2f11a11bbe2d@foss.st.com> 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: Sun, 15 Jan 2023 18:43:53 +0100 > CC: > From: Torbjorn SVENSSON > > 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? There's any number of potential problems that could potentially happen in the future. If we start worrying about all of them, we will have no time to do anything useful. Let's worry about problems that really happen when they happen.