RE: CVS Build Failure Cygwin 1.1.2 PC

[Jan Reimers <janr at molienergy dot bc dot ca>]

> -----Original Message-----
> From: Tim Prince [mailto:tprince@computer.org]
> Sent: Wednesday, August 09, 2000 5:27 PM
> To: Jan Reimers; gcc-bugs@gcc.gnu.org
> Subject: Re: CVS Build Failure Cygwin 1.1.2 PC
> 
> 
> The header file directories must be copied into the 
> appropriate place in
> the --prefix directory e.g. /usr/local/gcc/include just as if 
> this were
> a cross compile.  
OK I did this, but looking at the list of include directories I see this is
not one of them:

-isystem /usr/local/src/gcc/winsup/include 
-isystem /usr/local/src/gcc/winsup/cygwin/include 
-isystem /usr/local/src/gcc/winsup/w32api/include 
-isystem /usr/local/src/gcc/newlib/libc/sys/cygwin 
-isystem /usr/local/src/gcc/newlib/libc/sys/cygwin32 
-nostdinc
-isystem /usr/local/src/build/i586-pc-cygwin/newlib/targ-include 
-isystem /usr/local/src/gcc/newlib/libc/include 
-isystem /usr/local/gcc/i586-pc-cygwin/include

I chose to populate the last one with headers as it was the only outside my
build area (/usr/local/src).  I still find this odd, as I used to build gcc
2.95.x with --prefix=/usr/local wihtou any need populate /usr/local/include
or /usr/local/i586-pc-cygwin/include with headers.  Have things changed
since 2.95.x or does --prefix=/use/local get special treatment?


> Best not to use a sym-link, as it is possible to
> corrupt the original g++ installation.  
Right.

> Probably a good idea to bring
> your cygwin up to date by running latest/setup.

I will do this.  Thanks for your help.

JR