From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7326 invoked by alias); 26 Nov 2010 12:52:54 -0000 Received: (qmail 7309 invoked by uid 22791); 26 Nov 2010 12:52:53 -0000 X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout21.012.net.il (HELO mtaout21.012.net.il) (80.179.55.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 26 Nov 2010 12:52:47 +0000 Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0LCH00J00SZ1BE00@a-mtaout21.012.net.il> for gdb-patches@sourceware.org; Fri, 26 Nov 2010 14:52:34 +0200 (IST) Received: from HOME-C4E4A596F7 ([84.229.63.39]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LCH00JPFT3L1G90@a-mtaout21.012.net.il>; Fri, 26 Nov 2010 14:52:34 +0200 (IST) Date: Fri, 26 Nov 2010 12:52:00 -0000 From: Eli Zaretskii Subject: Re: Fix doc index name on Windows In-reply-to: <201011261203.05391.pedro@codesourcery.com> To: Pedro Alves Cc: gdb-patches@sourceware.org, jifl@ecoscentric.com Reply-to: Eli Zaretskii Message-id: <83d3ps6y9b.fsf@gnu.org> References: <4CEE9F77.1070509@eCosCentric.com> <4CEEAF36.7030005@eCosCentric.com> <83ipzk70w4.fsf@gnu.org> <201011261203.05391.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-11/txt/msg00453.txt.bz2 > From: Pedro Alves > Date: Fri, 26 Nov 2010 12:03:05 +0000 > Cc: Jonathan Larmour > > On Friday 26 November 2010 11:57:47, Eli Zaretskii wrote: > > Then it's a bug in the cross-build version of makeinfo. There's code > > in makeinfo/node.c:cm_node to handle the case when a file name > > produced from a node name clashes with a name of an existing file > > (produced from some other node name), due to limitations of the > > underlying filesystem. What makeinfo does in that case is put all the > > nodes whose names map to the same file name on that single file. I > > see this behavior in action in the Windows port of makeinfo 4.8, and > > the code which does this was written long before Texinfo 4.7 was > > released, so you must have it as well. > > If such code is only triggerable on some hosts only, then IMO it > is broken, because the resulting files will not be movable between > hosts (e.g., generate on Unix, unpack on Windows/NTFS/FAT/Samba, whatnot). IMO, "broken" is an exaggeration. How many tools did you see that care about having their files produced on Unix be compatible with NTFS? How many maintainers of GNU packages do you know who would even consider a possibility of inserting NTFS-related limitations into their codebase? Usually, such problems are at best fixed for the hosts that use the affected filesystems. And the cross-build environments should take care of these issues, because they _do_ (or should) care. > Is there a way to force that behaviour with a makeinfo command line > switch or something of the sort? Not that I know of. No one has ever asked for that, AFAIK. But it should be trivial to add such a switch, now that I pointed to the code which does that.