| delorie.com/archives/browse.cgi | search |
| From: | "A. Sinan Unur" <asu1 AT cornell DOT edu> |
| Newsgroups: | comp.os.msdos.djgpp |
| Subject: | Re: Long filename support? |
| Date: | Thu, 10 Jul 1997 09:08:14 -0400 |
| Organization: | Cornell University |
| Lines: | 35 |
| Sender: | asu1 AT cornell DOT edu (Verified) |
| Message-ID: | <33C4DEBE.3FBC@cornell.edu> |
| References: | <33C4CFA9 DOT 7D3C AT ricardis DOT tudelft DOT nl> |
| NNTP-Posting-Host: | 128 |
| Mime-Version: | 1.0 |
| To: | djgpp AT delorie DOT com |
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Ivo Janssen wrote:
> I have a little C-program which tries to include very_long_name.h
> by means of
> #include <very_long_name.h>
>
> Then gcc says: very_long_name.h: No such file or directory (ENOENT)
>
> So I change the filename in the .c-file in
> #include <very_l~1.h>
> and _don't_ change the filename on disk, and everything compiles
> wonderfully....
>
> So far for LFN support under DJGPP ?????
attitude ... anyway:
did you set +LFN=y in djgpp.env or used any of the other methods for
enabling long filenames mentioned in the FAQ.
the following compiles fine for me:
#include "longfilename.h"
int main(void)
{
return 0;
}
(if you are going to use <..> make sure the header file is in one of
the paths referenced in djgpp.env.)
next time, make sure djgpp is not the first thing you fault.
-- Sinan
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |