-----Original Message----- From: "Lee Rhodes" <lee@xxxxxxxxx> To: <gcc-help@xxxxxxxxxxx> Date: Fri, 22 Jun 2007 10:27:24 -0700 Subject: Re: Help compiling gcc 4.2.0 Brian, Thanks! You were right. I had used Winzip to unpack the tarballs! I unpacked using tar and the compile of C and C++ completed after 2 hrs and 45 min. Testing with 'make check-gcc', with the following results: === gcc Summary === # of expected passes 43665 # of unexpected failures 14 # of unexpected successes 1 # of expected failures 114 # of untested testcases 35 # of unsupported tests 361 /src/gcc-obj/gcc/xgcc version 4.2.0 === g++ Summary === # of expected passes 13574 # of unexpected failures 26 # of unexpected successes 3 # of expected failures 66 # of unsupported tests 168 /src/gcc-obj/gcc/testsuite/g++/../../g++ version 4.2.0 How should I interpret the above? In searching the gcc.log and g++.log files I did not find undefined references to _ungetc, __srget_r (wrt msg00948.html below), but did find a few other undefined references that did result in FAILs: e.g., _mcount,__monstartup. I don't have "Mail:" configured in cygwin so I can't use the test_summary script. Can I tar.gz up the gcc.sum, gcc.log, g++.sum, g++.log files and send it to gcc-testresults@xxxxxxxxxxx? Or is there a particular structure for these results. ________________________________________----- Use the test_summary script and paste the output into any reasonable e-mail compose window. I have submitted PRs on a few of the cygwin specific failures which could be avoided by simple corrections to the test. The one about profiling is due to the test script not permitting Cygwin the use of -pg rather than -p, as a few targets are permitted to do. So, once you fix your <stdio.h>, other failures are pretty much expected on Cygwin, although they are not set up as such in the testsuite. You could search the Cygwin archives for acknowledgments about the deficiencies of current Cygwin exception handling for g++, for example. Tim Prince
