Mail Archives: djgpp/1997/10/19/11:38:42
On Wed, 15 Oct 1997, Michal Mertl wrote:
> I also have problems with lfns; I have read Eli wrote that DJGPP 2.02 will
> have lfn=y as default setting, but wan't it cause problems when it runs
> on plain dos?
No. The DJGPP startup code queries the filesystem to see if the LFN
API is supported, and turns the LFN support off if it isn't. Setting
LFN=y doesn't override this detection process; only LFN=n
unconditionally turns the LFN support off.
> Is the djgpp long to short name conversion the same as W95's
> with NameNumericTail=0 ?
DJGPP doesn't truncate any file names at all. When your DJGPP program
uses non-LFN DOS functions, it is DOS that truncates the names. When
you use LFN-aware functions, the short 8+3 alias is invented by
Windows. Either way, DJGPP has nothing to do with the truncation
(except, maybe, that it reveals some subtle but grave bugs in it ;-).
> I get to this problem because to be able to try libsocket I had to enable
> lfns. If I set lfn=y I can't use info because I have my info files
> gzipped. It seems to me that gzip (from djgpp archives) never use lfns, am
> I correct, it always creates files with only one dot in name?
It's true that the current port of gzip doesn't support LFN, but I
don't see how is this relevant to compressed Info files. Info invokes
`gunzip' by opening a pipe to the following command:
gunzip < foo.info.gz
This should work regardless of the name of the file that is to be
decompressed. So please explain more about how do compressed Info
files fail for you, because they should work under both LFN=y and
LFN=n.
> Also I had some problems trying to use gzipped info files, e.g. files
> gcc.i1-gcc.i20 can't be compressed because gzip adds z to the end of the
> extension so gcc.i1 becomes gcc.i1z aswell as gcc.i11-19. So I had to
> rename the files to gcc1-20 and accordingly change the section filenames
> in gcc.inf file.
On Windows 95, you need to call these files gcc.i1.gz, gcc.i2.gz, ...,
gcc.i20.gz, just as you would do on Unix, and Info should then be able
to find them.
For LFN=n, the readme.djg file in the Texinfo distribution
(txi390b.zip) has a section which explains how to call your compressed
files to have Info uncompress them on the fly; please make sure your
files are called as that section suggests when you run with LFN disabled.
- Raw text -