delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/08/23/11:22:12

Date: Sun, 23 Aug 1998 18:21:40 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Endlisnis <s257m AT unb DOT ca>
cc: djgpp AT delorie DOT com
Subject: Re: long header file names possible in gcc NT 4.0?
In-Reply-To: <35E02791.8EA28C68@unb.ca>
Message-ID: <Pine.SUN.3.91.980823181453.1451B-100000@is>
MIME-Version: 1.0

On Sun, 23 Aug 1998, Endlisnis wrote:

> Eli Zaretskii wrote:
> 
> > > > does this mean that long header file names are not supported at all by gcc
> > > > under NT?
> > >     In the standard package, yes.  If you wish to fix the problem,
> > > then ensure you have "SET LFN=n" in your autoexec.bat file
> > Not needed.  DJGPP startup code will see that the LFN API isn't
> > supported and will turn it off automatically, even if you set LFN=y.
> 
>     I've had many problems running DJGPP under NT.  RHIDE will not work, it always
> crashes with error message 'Divide Overflow' during the first screen write.  None
> of the compiler programs would run properly until 'LFN=n' was set.  GCC would do
> screwy things like write random ASCII characters to the screen.  After 'LFN=n' was
> set, everything except RHIDE worked.

I don't use RHIDE, but everything else in DJGPP works for me on NT, even 
if I set LFN=y.  Please report specific problems in every utility that 
requires LFN=n on NT.  Please submit detailed reports, e.g. if GCC 
doesn't work, run it with -v and post everything that gets printed.

I'm not aware of any DJGPP utility that needs LFN=n on NT.  It might be 
something specific to your system configuration.

Did you maybe install the alpha version of the NT LFN server?

>     And, when compiled (using the same batch file) under NT & 95, yeild different
> EXE's (the one created under NT was about 1k bigger).  And the NT-compiled exe
> crashes on both machines.

This sounds like a currupted installation, or a bad linker (did that 
friend install RSXNTDJ at some point?).  I suggest to make a clean 
installation from the latest binaries and try again.

>     We've tried that, with no effect.  We had to rename all files with longer than
> 8.3 names to their truncated 8.3 version.

As the FAQ clearly says, disabling numeric tails only affects files 
created *after* the numeric tails were disabled.  It doesn't do anything 
to files that already exist.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019