Date: Sun, 9 May 1999 12:00:57 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Tokihiro Funakoshi <Kiyokofunakoshi AT email DOT msn DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: #include problem
In-Reply-To: <e0CqG9#l#GA.60@cpmsnbbsa02>
Message-ID: <Pine.SUN.3.91.990509120019.3278L-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 6 May 1999, Tokihiro Funakoshi wrote:

> Well the error was that every time there is an include command e.g.:
> #include <stdio.h>
> The computer states the filename which the command is in, followed by a
> colon, followed by the line which the command is in, followed by another
> colon,  then says "No such file or directory <ENOENT>"

This is covered by section 8.1 of the DJGPP FAQ list (v2/faq211b.zip
from the same place you get DJGPP).  The most probable cause of such
problems is that you didn't set the DJGPP environment variable
correctly.

Add -v to the compilation command line and watch the include path
printed by the compiler; you should see the `include' subdirectory of
your DJGPP main directory there.  If you don't see it, check the
setting of the DJGPP variable in the environment, as the FAQ explains.