Lee, Building took only two hours 45 minutes? I'm jealous. :) At about 2:00 AM, I told my Sunblade 100 workstation Tamino to build gcc-4.2.0. Instantly, he began to clink, to clank, and to clunk, and stopped "drumming" at about 9:45 PM that night. Some guys get all the luck. ;) Bill > 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. > > Thanks for the help > > Lee. > > P.S. Sorry about the dual post, I didn't realize the lists were connected. > > > > > -----Original Message----- > From: Brian Dessent [mailto:brian@xxxxxxxxxxx] > Sent: Thursday, June 21, 2007 2:20 PM > To: Lee Rhodes > Cc: gcc-help@xxxxxxxxxxx > Subject: Re: Help compiling gcc 4.2.0 > > Lee Rhodes wrote: > > > I am struggling with the infamous unix/dos end-of-line '\r\n' vs '\n' > > incompatibilities. It seems that no matter what shell I use (bash, > > sh, Cygwin, rxvt, dos) that the gnu make utility throws errors when it > > sees the '\r' CR character. > > > > Do I have to convert ALL the downloaded files into the unix format > > (dos2unix)? (Yikes!) or is there a global setting that I can use so > > that I don't have to do that. > > There are no CRs anywhere in the source code tarballs. If you are seeing > any, they are a result of the method you used to unpack them locally. This > means you either didn't choose binary mode for your mounts or you used a > non-Cygwin tool such as Winzip to unpack the tarballs. In either case, > don't do that. There should never be a need to convert anything. > > Also, you'll need to use a Cygwin snapshot to build gcc otherwise you'll run > into <http://gcc.gnu.org/ml/gcc/2007-03/msg00948.html> which has been fixed > for some time, but the last Cygwin release was a while ago. > > Brian > > > ________________________________________________________________ Please visit a saintly hero: http://www.jakemoore.org And a boy with a wonderful wish: http://shaneswish.com/
