X-Authentication-Warning: ieva01.lanet.lv: pavenis owned process doing -bs
Date: Mon, 16 Nov 1998 22:29:49 +0200 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc: Daniel McGrath <dmcg6174 AT yahoo DOT com>, djgpp AT delorie DOT com
Subject: Re: Problem with nested #include's
In-Reply-To: <Pine.SUN.3.91.981116131810.8173D-100000@is>
Message-ID: <Pine.A41.4.05.9811162226300.129752-100000@ieva01.lanet.lv>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com


Specifying full path seems to work with both egcs-1.1 and gcc-2.8.1
(version of June 1998, I had it on CD, didn't want to mess with
installing).

#include  "C:xxxx..." does not work. But does we really need it

Andris 

On Mon, 16 Nov 1998, Eli Zaretskii wrote:

> 
> On Sun, 15 Nov 1998, Daniel McGrath wrote:
> 
> > Actually, I am writing out the file names, complete with the drive
> > letter and the path (i.e., "#include "c:/.../bar.h" (or baz.h)).
> 
> This seems to be a bug in cpp: it fails to recognize that "c:/foo" is an 
> absolute file name.  (Andris, does this happen in the latest versions of 
> GCC/EGCS as well?)
> 
> But I think that you should avoid using absolute file names in include 
> directives, since it is inherently non-portable and ANSI C doesn't 
> specify what should happen in this case.  Just say <baz.h> and add 
> -Ic:/whatever to the GCC command line.
>