* Why can't I build a native i686-pc-cygwin compiler?
@ 2003-12-03 23:39 aspiesrule
0 siblings, 0 replies; 3+ messages in thread
From: aspiesrule @ 2003-12-03 23:39 UTC (permalink / raw)
To: gcc
I am trying to build a native compiler for i686-pc-cygwin. I use Cygwin
version 1.5.5 on Windows NT 5.1. I can configure just fine (here is the
cmdline for the configure script: "~/gcc-build/configure --
prefix=${HOME}/gcc-objs --with-gnu-as --with-gnu-ld --disable-werror --
enable-checking=misc,tree,gc,rtl,rtlflag,fold,gcac") but "make bootstrap"
fails with an error. The error message and associated make verbiage are as
follows:
stage1/xgcc.exe -Bstage1/ -B/home/Lucas/gcc-objs/i686-pc-cygwin/bin/ -g -
O2 -D
IN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -
peda
ntic -Wno-long-long -Wold-style-definition -fno-common -DHAVE_CONFIG_H -
DGENE
RATOR_FILE -o genattrtab.exe \
genattrtab.o genautomata.o \
rtl.o read-rtl.o bitmap.o ggc-none.o min-insn-modes.o gensupport.o insn-
conditi
ons.o print-rtl1.o errors.o \
varray.o ../libiberty/libiberty.a -lm
/genattrtab.exe /home/Lucas/gcc-build/gcc/config/i386/i386.md > tmp-
attrtab.c
Check description...done
Reservation transformation...done
Check unit distributions to automata...done
Prepare automaton `pentium' creation...done
Create automaton `pentium' (1 star is 100 new states): done
Make DFA `pentium' (1 star is 100 new states): done
Minimize DFA `pentium'...done
Prepare automaton `pentium_fpu' creation...done
Create automaton `pentium_fpu' (1 star is 100 new states): done
Make DFA `pentium_fpu' (1 star is 100 new states): done
Minimize DFA `pentium_fpu'...done
Prepare automaton `athlon' creation...done
Create automaton `athlon' (1 star is 100 new states):***** done
Make DFA `athlon' (1 star is 100 new states): done
Minimize DFA `athlon'...done
Prepare automaton `athlon_load' creation...done
Create automaton `athlon_load' (1 star is 100 new states):* done
Make DFA `athlon_load' (1 star is 100 new states): done
Minimize DFA `athlon_load'...done
Prepare automaton `athlon_mult' creation...done
Create automaton `athlon_mult' (1 star is 100 new states): done
Make DFA `athlon_mult' (1 star is 100 new states): done
Minimize DFA `athlon_mult'...done
Prepare automaton `athlon_fp' creation...done
Create automaton `athlon_fp' (1 star is 100 new
states):************************
*****************************************************************************
***
*************************************************** done
Make DFA `athlon_fp' (1 star is 100 new states): done
Minimize DFA `athlon_fp'...done
Generation of attributes...done
All other genattrtab stuff...done
Forming and outputting automata tables...done
Output functions to work with automata...done
Automaton `pentium'
48 NDFA states, 138 NDFA arcs
48 DFA states, 138 DFA arcs
20 minimal DFA states, 82 minimal DFA arcs
158 all insns 17 insn equivalence classes
91 transition comb vector els, 340 trans table els: use comb vect
91 state alts comb vector els, 340 state alts table els: use comb vect
340 min delay table els, compression factor 2
Automaton `pentium_fpu'
80 NDFA states, 172 NDFA arcs
80 DFA states, 172 DFA arcs
75 minimal DFA states, 162 minimal DFA arcs
158 all insns 8 insn equivalence classes
164 transition comb vector els, 600 trans table els: use comb vect
164 state alts comb vector els, 600 state alts table els: use comb vect
600 min delay table els, compression factor 1
Automaton `athlon'
518 NDFA states, 1668 NDFA arcs
518 DFA states, 1668 DFA arcs
76 minimal DFA states, 328 minimal DFA arcs
158 all insns 10 insn equivalence classes
382 transition comb vector els, 760 trans table els: use simple vect
382 state alts comb vector els, 760 state alts table els: use simple vect
760 min delay table els, compression factor 2
Automaton `athlon_load'
162 NDFA states, 855 NDFA arcs
162 DFA states, 855 DFA arcs
162 minimal DFA states, 855 minimal DFA arcs
158 all insns 10 insn equivalence classes
1039 transition comb vector els, 1620 trans table els: use simple vect
1039 state alts comb vector els, 1620 state alts table els: use simple vect
1620 min delay table els, compression factor 2
Automaton `athlon_mult'
16 NDFA states, 48 NDFA arcs
16 DFA states, 48 DFA arcs
16 minimal DFA states, 48 minimal DFA arcs
158 all insns 4 insn equivalence classes
52 transition comb vector els, 64 trans table els: use simple vect
52 state alts comb vector els, 64 state alts table els: use simple vect
64 min delay table els, compression factor 2
Automaton `athlon_fp'
15522 NDFA states, 99908 NDFA arcs
15522 DFA states, 99908 DFA arcs
463 minimal DFA states, 3038 minimal DFA arcs
158 all insns 21 insn equivalence classes
3051 transition comb vector els, 9723 trans table els: use comb vect
3051 state alts comb vector els, 9723 state alts table els: use comb vect
9723 min delay table els, compression factor 1
17012 all allocated states, 101385 all allocated arcs
20258 all allocated alternative states
4779 all transition comb vector els, 13107 all trans table els
4779 all state alts comb vector els, 13107 all state alts table els
13107 all min delay table els
0 locked states num
transformation: 0.031000, building DFA: 6.625000
DFA minimization: 0.641000, making insn equivalence: 0.000000
all automaton generation: 7.359000, output: 0.125000
/bin/sh /home/Lucas/gcc-build/gcc/move-if-change tmp-attrtab.c insn-attrtab.c
insn-attrtab.c is unchanged
echo timestamp > s-attrtab
stage1/xgcc.exe -Bstage1/ -B/home/Lucas/gcc-objs/i686-pc-cygwin/bin/ -g -
O2 -D
IN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -
peda
ntic -Wno-long-long -Wold-style-definition -fno-common -
DHAVE_CONFIG_H -I.
-I. -I/home/Lucas/gcc-build/gcc -I/home/Lucas/gcc-build/gcc/. -
I/home/Lucas/gcc
-build/gcc/../include -c insn-attrtab.c \
-o insn-attrtab.o
make[2]: *** [insn-attrtab.o] Error 1
make[2]: Leaving directory `/home/Lucas/gcc-objs/gcc'
make[1]: *** [stage2_build] Error 2
make[1]: Leaving directory `/home/Lucas/gcc-objs/gcc'
make: *** [bootstrap] Error 2
What went wrong here? Is this a bug in the Makefile, make, cygwin.dll, or
something else entirely?
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: Why can't I build a native i686-pc-cygwin compiler?
@ 2003-12-04 21:11 Billinghurst, David (CALCRTS)
0 siblings, 0 replies; 3+ messages in thread
From: Billinghurst, David (CALCRTS) @ 2003-12-04 21:11 UTC (permalink / raw)
To: aspiesrule, gcc
> From: aspiesrule@mcleodusa.net [mailto:aspiesrule@mcleodusa.net]
> Sent: Thursday, 4 December 2003 10:15 AM
> To: gcc@gcc.gnu.org
> Subject: Why can't I build a native i686-pc-cygwin compiler?
>
>
>
> I am trying to build a native compiler for i686-pc-cygwin. I use Cygwin
> version 1.5.5 on Windows NT 5.1.
I build gcc-3.3 and gcc mainline from CVS most nights and post the results
to gcc-testresults@gcc.gnu.org. I haven't done so this week as I have am
travelling, so I don't know if the problem you report was intoduced recently.
I suggest that you for a start you either:
- build gcc from the current cygwin release sources
- see if you can build a recent gcc release
- have a look at the archives and see if you can build the CVS code
from a date/time that is known to work
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Why can't I build a native i686-pc-cygwin compiler?
[not found] <E1ARgBm-0002BD-00@deer.gmane.org>
@ 2003-12-04 20:26 ` Jim Wilson
0 siblings, 0 replies; 3+ messages in thread
From: Jim Wilson @ 2003-12-04 20:26 UTC (permalink / raw)
To: aspiesrule; +Cc: gcc
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-12-04 21:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-12-03 23:39 Why can't I build a native i686-pc-cygwin compiler? aspiesrule
[not found] <E1ARgBm-0002BD-00@deer.gmane.org>
2003-12-04 20:26 ` Jim Wilson
2003-12-04 21:11 Billinghurst, David (CALCRTS)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).