Newbie: problems building gcc 2.95.2
Tue Nov 30 23:39:00 GMT 1999

In a message dated 11/23/99 6:24:31 PM Pacific Standard Time, 

> $ bash /usr/local/src/gcc-2.95.2/configure -v i586-cygwin32
>  this works fine
>  $ make > make.log 2>&1
>  this fails with
>  /usr/local/src/gcc-2.95.2/gcc/libgcc2.c:41: stdlib.h: No such file or
>  directory
>  /usr/local/src/gcc-2.95.2/gcc/libgcc2.c:42: unistd.h: No such file or
>  directory

Under cygwin, configure doesn't do a good job of guessing the --host and 
--target designations.  Supposing that you know it's going to default those 
to i586-pc-cygwin32, it would be a good idea to make sure that the implied 
include directories are populated prior to building.  I suppose these would 
be /usr/local/i586-pc-cygwin32/include and 
/usr/local/lib/gcc-lib/i586-pc-cygwin32/2.95.2/include.  Actually, if you are 
using a i586-cygwin32 compiler to build a i586-pc-cygwin32 compiler, it may 
work best to install a cygwin snapshot of the i586-pc-cygwin32 variety, 
'configure --host=i586-cygwin32 --target=i586-pc-cygwin32','make 
LANGUAGES=c','make LANGUAGES=c' install, thus accomplishing the creation of 
the necessary directories, then reconfigure with --host=i586-pc-cygwin32, 
'make LANGUAGES=c bootstrap-lean', following up by 'make LANGUAGES='c++ f77' 
if those are the ones you want. I would expect trouble later on if you build 
a i586-pc-cygwin32 clone of the i586-cygwin32 setup, without the snapshot 
changes.  When you say the configure works fine, did you check to make sure 
that /usr/local/build/gcc-2.95.2/gcc/Makefile etc were done?  I'm sure this 
will create disagreements, but I'm not certain exactly what you are trying to 
do.  If you are trying to rebuild Mumit Khan's version of the compilers, you 
will need his source patches.  It's been quite a while since I ran configure 
under bash and make-3.75, so I'm not sure what's going to happen.


Want to unsubscribe from this list?
Send a message to

More information about the Cygwin mailing list