Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <5.2.0.9.2.20021212085030.02c59bf8@pop3.cris.com>
X-Sender: rrschulz AT pop3 DOT cris DOT com
Date: Thu, 12 Dec 2002 08:54:11 -0800
To: cygwin AT cygwin DOT com
From: Randall R Schulz <rrschulz AT cris DOT com>
Subject: Re: Why "No such file ..." in path ? 1.3.17
In-Reply-To: <5.2.0.9.2.20021211191706.02b9d510@pop3.cris.com>
References: <4DD92E5BC22B8E41AA3C5FF13351CF696097A0 AT cmrdsrv DOT cmrd DOT panaso nic.com.cn>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Kun,

I need to correct myself (since no one else did!)...

At 19:30 2002-12-11, Randall R Schulz wrote:
>Kun,
>
>...
>
>Include files required during C or C++ compilation are located via a 
>separate search path maintained by the compiler and not driven by any 
>environment variable, at least not in the Cygwin compiler, which is GCC.

There _are_ environment variables to tell GCC where to find files. This is 
an excerpt from the (rather long) man page for "gcc":

-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-
Some additional environments variables affect the behavior
of the preprocessor.

CPATH

C_INCLUDE_PATH

CPLUS_INCLUDE_PATH

OBJC_INCLUDE_PATH
     Each variable's value is a list of directories
     separated by a special character, much like PATH, in
     which to look for header files.  The special
     character, PATH_SEPARATOR, is target-dependent and
     determined at GCC build time.  For Windows-based
     targets it is a semicolon, and for almost all other
     targets it is a colon.

     CPATH specifies a list of directories to be searched
     as if specified with -I, but after any paths given
     with -I options on the command line.  The environment
     variable is used regardless of which language is being
     preprocessed.

     The remaining environment variables apply only when
     preprocessing the particular language indicated.  Each
     specifies a list of directories to be searched as if
     specified with -isystem, but after any paths given
     with -isystem options on the command line.
-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-


I believe the rest of what I wrote was accurate.

Randall Schulz
Mountain View, CA USA


>...
>
>Randall Schulz
>Mountain View, CA USA
>
>
>At 19:08 2002-12-11, Wu Kun wrote:
>>Hi, all:
>>
>>When I use CygWin 3.17.1 to build Sun's CLDC 1.0.x, an error occurs:
>>
>>../../src/check_class.c(30) : fatal error C1083: Cannot open include
>>file: 'ctype.h': No such file or directory
>>
>>But the file "ctype.h" is right in the /usr/include, which has been set
>>in the $PATH.
>>
>>
>>Can some body help me out ?
>>
>>Best Regards
>>
>>Wu Kun


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/