Date: Mon, 16 Nov 1998 13:21:21 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Daniel McGrath <dmcg6174 AT yahoo DOT com>, Andris Pavenis <pavenis AT lanet DOT lv>
cc: djgpp AT delorie DOT com
Subject: Re: Problem with nested #include's
In-Reply-To: <364f5d7b.5753228@news.liii.com>
Message-ID: <Pine.SUN.3.91.981116131810.8173D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com


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.