This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Failed building GCC 4.1.2 on Cygwin
- From: Brian Dessent <brian at dessent dot net>
- To: cygwin at cygwin dot com
- Date: Tue, 27 Mar 2007 21:00:15 -0700
- Subject: Re: Failed building GCC 4.1.2 on Cygwin
- References: <loom.20070328T052946-753@post.gmane.org>
- Reply-to: cygwin at cygwin dot com
wei wrote:
> After compiling nearly one hour,it stopped and reported the errors below:
>
> gcc -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissi
> ng-prototypes -Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG
> _H -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include -I./../i
> ntl -I../../gcc/gcc/../libcpp/include \
> -DHOST_MACHINE=\"i686-pc-cygwin\" -DTARGET_MACHINE=\"i686-pc-cygwin\" \
> ../../gcc/gcc/c-pch.c -o c-pch.o
> gcc: no input files
> F:\cygwin\bin\make.exe[2]: *** [c-pch.o] Error 1
> F:\cygwin\bin\make.exe[2]: Leaving directory `f:/temp/build/gcc'
> F:\cygwin\bin\make.exe[1]: *** [all-gcc] Error 2
> F:\cygwin\bin\make.exe[1]: Leaving directory `f:/temp/build'
> F:\cygwin\bin\make.exe: *** [all] Error 2
This is not nearly enough information to help. For one thing, why are
there win32 paths here? If you're trying to build a native gcc there
should be only POSIX paths. It looks a little like you've got a mix of
MinGW and Cygwin tools thrown together (which won't work very well) but
I don't know why you'd have a MinGW make in /usr/bin. Also, we need to
know the exact configure options used. And cygcheck output. And so on.
> I'm a newcomer here.Please help me! Thanks in advance!
Compiling gcc is not something a newcomer should do. If you just want
gcc installed, select the package in setup.exe.
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/