This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Why can't I build a native i686-pc-cygwin compiler?
- From: Jim Wilson <wilson at specifixinc dot com>
- To: aspiesrule at mcleodusa dot net
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 04 Dec 2003 12:19:59 -0800
- Subject: Re: Why can't I build a native i686-pc-cygwin compiler?
- References: <E1ARgBm-0002BD-00@deer.gmane.org>
aspiesrule@mcleodusa.net wrote:
I am trying to build a native compiler for i686-pc-cygwin.
What went wrong here? Is this a bug in the Makefile, make, cygwin.dll, or
something else entirely?
It isn't possible for us to tell what went wrong here. There was no
error printed in the output before make failed.
You didn't mention what gcc version you are trying to build. If you are
trying to building from mainline, then then keep in mind that these are
development sources, and they are occasionally broken.
The first thing I would suggest is try continuing the build by running
make bootstrap again. If this is a real gcc bug, then it will be
reproducible, i.e. it will fail at the same place everytime. If it
doesn't always fail at the same place, then the bug could be in some
other part of the system. Some PC hardware can be unreliable, e.g.
overclocked systems, systems with memory that is starting to fail, etc.,
and this may show up while building gcc because gcc stresses the system
by using lots of memory.
If this is a real gcc bug, then you should try to debug the problem.
Run gcc (or rather cc1) under gdb to see where it is failing, and try to
figure out why. You might also look to see if a recent patch might
explain the failure. If a build worked last week, but not today, then a
patch checked in since then must have broken it.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com