Xref: news2.mv.net comp.os.msdos.djgpp:8372
From: "John M. Aldrich" <fighteer AT cs DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Additional include directories
Date: Fri, 06 Sep 1996 18:46:32 -0700
Organization: Three pounds of chaos and a pinch of salt
Lines: 35
Message-ID: <3230D3F8.D50@cs.com>
References: <199609061336 DOT PAA18790 AT ohm DOT fast DOT co DOT za>
NNTP-Posting-Host: ppp203.cs.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Alf Stockton <stockton AT fast DOT co DOT za>
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Alf Stockton wrote:
> 
> I want gcc, or rather the preprocessor, to find my #include files in a
> subdirectory other than the normal setup in DJGPP.ENV and so I altered the
> C_INCLUDE_PATH line in DJGPP.ENV to the following :-
> C_INCLUDE_PATH=%/>;C_INCLUDE_PATH%%DJDIR%/include;%DJDIR%/contrib/grx20/incl
> ude;d:\dev\gcc\panelp.213\include
> but for some reason cpp cannot locate files in d:\dev\gcc\panelp.213\include.
> 
> What have I done wrong ?

Use forward slashes, like the rest of the directories in the C_INCLUDE_PATH.
Either that or escape your backslashes by using '\\' in place of '\'.  A
single '\' is the escape character under Unix and C.  There should be no
problem with drive specifiers; if there are, please repost.  If you do so,
be sure to include the output of gcc when invoked with the -v command.
Do this like so:

redir -o gcc.out -eo gcc -v [...]

Include the resulting gcc.out file with your post, as well as the entire
contents of your DJGPP.ENV.

Hope this helps!

John <fighteer AT cs DOT com>

-- 
                      Anything that happens, happens.
    Anything that, in happening, causes something else to happen, causes
                         something else to happen.
 Anything that, in happening, causes itself to happen again, happens again.
        It doesn't necessarily do it in chronological order, though.
 
                                       --- Douglas Adams