Message-ID: From: "Andris Pavenis" To: Eli Zaretskii Date: Wed, 20 Jan 1999 12:49:55 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: autoconf 2.13 test version available CC: "Mark E." , djgpp-workers AT delorie DOT com References: In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.01d) Reply-To: djgpp-workers AT delorie DOT com On 20 Jan 99, at 10:02, Eli Zaretskii wrote: > > On Wed, 20 Jan 1999, Andris Pavenis wrote: > > > I have not it tested very seriously with LFN=N. Maybe I have something > > else broken with LFN=N as I didn't use NameNumericTail=0 and only > > reinstalled autoconf-2.13 from my binary archive with LFN=N under plain > > DOS > > Testing under plain DOS is even better than setting LFN=n on Windows > (since in the latter case, COMMAND.COM and other Windows programs still > see the long names). > > FWIW, I also think that every person who develops DJGPP programs should > have NameNumericTail disabled. In fact, I don't see why anybody should > avoid disabling numeric tails. > > But what I was lamenting was not any specific case, but rather a series > of ports where people who made them specifically say they don't work > well, or won't build, without LFN support. I find this trend disturbing. > Yes it would be nice to have automake working Ok without LFN support. Unfortunatelly there are rather serious problems: - it's easy to change .deps to _deps in automake and some more files so this could be done - more serious thing is that config.h.in and similar files (many packages contains them). This is source of some more failures in tests. I think that trying to change something related in automake built for DJGPP without updating similary other packages will only break things So I'm afraid that we'll still have problems with automake when LFN=N. Andris