Date:	Sun, 25 Jun 2000 10:14:55 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Pat Ritchie <pritchie AT logikos DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: Autodependencies and long filenames with Windows NT.
In-Reply-To:	<8itler$o4d$1@news.sysnet.net.tw>
Message-ID:	<Pine.SUN.3.91.1000625101424.25761A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, 22 Jun 2000, Pat Ritchie wrote:

> First Example - Fails:
>     gcc -MM test.c
>     test.c:1: longfilename.h: No such file or directory (ENOENT)
> 
> Second Example - Passes:
>     gcc -MM test.c
>     test.o: test.c filename.h
> 
> The test.c file contains only a single line of code:
> First Example -
>     #include "longfilename.h"
> Second Example -
>     #include "filename.h"
> 
> Both files, longfilename.h and filename.h exist in the current directory.

I cannot reproduce this problem: "gcc -MM" works for me as expected in
this case.

Is it possible that you edited the file longfilename.h with some
Windows editor?  In that case, GCC cannot find longfilename.h because
the short 8+3 alias of longfilename.h is something like longfi~1.h
instead of longfile.h.  You need to use a DOS or DJGPP program to
create longfilename.h on NT, and then it will work.

Alternatively, you could install the LFN driver for NT, see section
3.3 of the FAQ for details.

- Raw text -