The standard gnu gcc-2.95.3 is not consistent with the current cygwin
win32api, so, at the very least, you must fix up [de]time_.c as well as
copying the cygwin include directory to your build target directory.
Standard gcc-2.95.3 has been used to build cross compilers from cygwin
to other architectures, but there really isn't any good reason for
avoiding the cygwin patched version when building a cygwin compiler.
There is more cygwin compatibility in the gcc-3.0 snapshots than in
"offcial" gcc-2.95.3.
----- Original Message -----
From: "Earnie Boyd" <[EMAIL PROTECTED]>
To: "Chris Telting" <[EMAIL PROTECTED]>
Cc: "Cygwin Users" <[EMAIL PROTECTED]>
Sent: Sunday, April 22, 2001 9:51 AM
Subject: Re: Building GCC
> Chris Telting wrote:
> >
> > > GCC doesn't build in the source directory. You should always try
to
> > > build in a build directory first.
> > >
> > > cd gcc-2.95.2
> > > mkdir build
> > > cd build
> > > ../configure --prefix=/your/prefix ...
> > > make
> > > make check ;#(there will be something like 16 failures).
> > > make install
> >
> > It still stopped at etime_.c because it can't find the windows
> > include directory. How do I tell the make process in include
> > that directory when it runs the new xgcc for compiling the
> > support libraries?
> >
> > I am sure I need to change some file somewhere since the official
> > gcc does not seem to know about a windows include directory and
> > the patch files don't resolve that issue.
> >
> > I'm puzzled how gcc knows to search w32api but the newly built
> > xgcc doesn't.
> >
> > How to I tell it to search w32api?
>
> It's controlled by the src/gcc/config/i386/cygwin.h file which defines
> the specs. You'll have to patch it to properly declare the
> /usr/include/w32api directory as a system include directory or simply
> replace it with the gcc-2.95.3-3 version.
>
> Earnie.
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
