From: Aaron W. L. <aar...@aa...> - 2004-09-06 00:45:26
|
make[1]: Entering directory `/aaronwl/cs/compilers/gcc/build/mingw-head/build-i686-pc-mingw32/fixincludes' gcc -c -g -O2 -DHAVE_CONFIG_H -I. -I../../../../src/cvs/head/gcc/fixincludes -I../include -I../../../../src/cvs/head/gcc/fixincludes/../include ../../../../src/cvs/head/gcc/fixincludes/fixincl.c ../../../../src/cvs/head/gcc/fixincludes/fixincl.c: In function `initialize': ../../../../src/cvs/head/gcc/fixincludes/fixincl.c:316: error: `SIGQUIT' undeclared (first use in this function) ../../../../src/cvs/head/gcc/fixincludes/fixincl.c:316: error: (Each undeclared identifier is reported only once ../../../../src/cvs/head/gcc/fixincludes/fixincl.c:316: error: for each function it appears in.) ../../../../src/cvs/head/gcc/fixincludes/fixincl.c:323: error: `SIGALRM' undeclared (first use in this function) ../../../../src/cvs/head/gcc/fixincludes/fixincl.c: In function `create_file': ../../../../src/cvs/head/gcc/fixincludes/fixincl.c:578: error: too many arguments to function `mkdir' ../../../../src/cvs/head/gcc/fixincludes/fixincl.c: In function `internal_fix': ../../../../src/cvs/head/gcc/fixincludes/fixincl.c:861: error: `F_DUPFD' undeclared (first use in this function) make[1]: *** [fixincl.o] Error 1 make[1]: Leaving directory `/aaronwl/cs/compilers/gcc/build/mingw-head/build-i686-pc-mingw32/fixincludes' Was fixincludes ever being built for i?86-pc-mingw before it the recent changes to put it in a toplevel directory? Should this be fixed by disabling fixincludes or by making fixincludes work on Windows? Is there any benefit in using fixincludes on Windows targets? Aaron W. LaFramboise |