This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
I wonder if there might be a chance of being able
to build egcs using cygwin-1.1.0
in the near future? I know that it has not been
possible during the egcs evolution
before. But, perhaps the time has come to
incorporate patches to the egcs
development branch to make it build under cygwin-1.1.0?
Right now, I can't get by the following error while
bootstrapping the compiler:
gcc -c -DIN_GCC -g -W -Wall
-Wtraditional -DHAVE_CONFIG_H -I.
-I../../egcs-20000417/gcc -I../../egcs-20000417/gcc/config
-I../../egcs-20000417/gcc/../include
../../egcs-20000417/gcc/config/i386/i386.c
../../egcs-20000417/gcc/config/i386/i386.c: In function `incdec_operand': ../../egcs-20000417/gcc/config/i386/i386.c:1143: warning: integer constant is unsigned in ANSI C, signed with -traditional ../../egcs-20000417/gcc/config/i386/i386.c: In function `i386_dwarf_output_addr_const': ../../egcs-20000417/gcc/config/i386/i386.c:2896: `INT_ASM_OP' undeclared (first use in this function) ../../egcs-20000417/gcc/config/i386/i386.c:2896: (Each undeclared identifier is reported only once ../../egcs-20000417/gcc/config/i386/i386.c:2896: for each function it appears in.) ../../egcs-20000417/gcc/config/i386/i386.c: In function `ix86_expand_int_movcc': ../../egcs-20000417/gcc/config/i386/i386.c:5013: warning: integer constant is unsigned in ANSI C, signed with -traditional ../../egcs-20000417/gcc/config/i386/i386.c: In function `ix86_expand_strlensi_unroll_1': ../../egcs-20000417/gcc/config/i386/i386.c:5896: warning: integer constant is unsigned in ANSI C, signed with -traditional make[2]: *** [i386.o] Error 1 Cheers,
/ChJ
|
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |