You didn't post enough of the log. Post the entire build log. I know it's large, but I'll bet it will be under the attachment size limit if you compress it.
Originally Posted by rbautch
Your build looks to be in the second stage of building gcc, after building glibc. My guess is that the glibc build failed, but the script keeps going anyway. I've seen that before. The last time, I tracked it down to an assumption in the glibc script that assumed a case sensitive file system (.oS and .os needed to be distinct file extensions). I fixed that problem, but apparently your build is still failing at the glibc stage for some other reason.
It did work for me under the very latest cygwin last week... You might update all your cygwin packages to the latest version and try again. Here's the information on the cygwin build I'm using:
% uname -srvmp
CYGWIN_NT-5.1 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 unknown
% gcc -v
Reading specs from /usr/lib/gcc/i686-pc-cygwin/3.4.4/specs
Configured with: /gcc/gcc-3.4.4/gcc-3.4.4-1/configure --verbose --prefix=/usr --exec-prefix=/usr --sysconfdir=/etc --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-languages=c,ada,c++,d,f77,java,objc --enable-nls --without-included-gettext --enable-version-specific-runtime-libs --without-x --enable-libgcj --disable-java-awt --with-system-zlib --enable-interpreter --disable-libgcj-debug --enable-threads=posix --enable-java-gc=boehm --disable-win32-registry --enable-sjlj-exceptions --enable-hash-synchronization --enable-libstdcxx-debug : (reconfigured)
Thread model: posix
gcc version 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125)