This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Fix doc index name on Windows

> 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.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]