Why "No such file ..." in path ? 1.3.17

Why "No such file ..." in path ? 1.3.17

[Wu Kun]

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


~~~~~~~~~~~~~~~~

Advance Mobil Communication Laboratories (AMCL) ,
Matsushita Research & Development (China) Co, Ltd (CMRD) 
URL : http://www.panasonic.com.cn/cmrd

18th Floor, Zhong-Guan-Cun Tower 
No.27, Zhong-Guan-Cun Street 
Beijing 100080
PR China 

E-mail : wukun@cmrd.panasonic.com.cn
Tel : +8610-82856490 , 82856424
Ext: 2036 , 2035
Fax : +8610-82856427

--
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/

Re: Why "No such file ..." in path ? 1.3.17

[Randall R Schulz]

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/

Re: Why "No such file ..." in path ? 1.3.17

[Randall R Schulz]

Kun,

The PATH environment variables is used only to find executables and the DLL 
(dynamically linked libraries) those executables require.


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.

You'll probably need to learn about the conventions and rules of C 
programming and compilers (and related tools such as "make") in order to be 
able to generalize the build scripts you're using.


By the way, is this the same CLDC whose home page is 
<http://java.sun.com/products/cldc/>? If so, are you also building the KVM 
yourself? If not, is the KVM also built with GCC? If these two components 
are not going to be built with the same compilers, then you must verify 
that the compilers' ABIs (application binary interfaces) are compatible, or 
the CLDC native library you're building will not be usable from the KVM.

It is a certainty that a Java Native Interface library built using GCC will 
not be able to be accessed from the Sun JVM for Windows.


Also, just to be pedantic, it's "Cygwin," not "CygWin."

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/