Re: Successfull Build of gcc on Cygwin WinXp SP2
Aaron Gray wrote: I tried doing 'make check' but it needed autogen which does not build on Cygwin apparently :( That's just the fixincludes dir. It's not important. This is why the instructions tell you to run make -k check. Okay I will try that. Oh 'make check' is the test suite, did not realize that. I thought it was a separate CVS branch/download. Anyway its been running ten hours now and got to struct-layout-1. Any clue as to how long it will run for ? Aaron -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Successfull Build of gcc on Cygwin WinXp SP2
Aaron Gray wrote: Any clue as to how long it will run for ? Depends on how many languages you enabled. In my case: c,c++,fortran,objc Bootstrapping the compilers took about 6 hours, and the testsuite took about 60. -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Successfull Build of gcc on Cygwin WinXp SP2
Has anyone already run the testsuite on GCC-4.3-20070427/Cygwin latest snapshot ? Got the following so far :- Running /usr/src/gcc-4.3-20070427/gcc/testsuite/gcc.dg/dg.exp ... FAIL: gcc.dg/20021014-1.c (test for excess errors) WARNING: gcc.dg/20021014-1.c compilation failed to produce executable FAIL: gcc.dg/Wstrict-overflow-11.c (test for excess errors) FAIL: gcc.dg/builtins-20.c (test for excess errors) FAIL: gcc.dg/builtins-59.c scan-tree-dump __builtin_cexpi FAIL: gcc.dg/builtins-59.c scan-tree-dump-not sincos FAIL: gcc.dg/builtins- 61.c scan-tree-dump cexpi FAIL: gcc.dg/builtins-61.c scan-tree-dump sin FAIL: gcc.dg/builtins-61.c scan-tree-dump cos FAIL: gcc.dg/builtins-61.c scan-tree-dump return 0.0 FAIL: gcc.dg/builtins-62.c scan-tree-dump-times cexpi 3 Anyone know how long this make check will take approximately ? Running about 12 hours so far. Aaron -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Successfull Build of gcc on Cygwin WinXp SP2
Any clue as to how long it will run for ? Depends on how many languages you enabled. In my case: c,c++,fortran,objc Bootstrapping the compilers took about 6 hours, and the testsuite took about 60. Okay, I have just done c, and c++. Have you got testsuite results, have you put them online at all ? Aaron -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Successfull Build of gcc on Cygwin WinXp SP2
On 03 May 2007 01:18, Aaron Gray wrote: Aaron Gray wrote: I tried doing 'make check' but it needed autogen which does not build on Cygwin apparently :( That's just the fixincludes dir. It's not important. This is why the instructions tell you to run make -k check. Okay I will try that. Oh 'make check' is the test suite, did not realize that. I thought it was a separate CVS branch/download. Anyway its been running ten hours now and got to struct-layout-1. Any clue as to how long it will run for ? Depends on your machine. Can easily be a couple of days. :-O cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Successfull Build of gcc on Cygwin WinXp SP2
On 03 May 2007 02:43, Aaron Gray wrote: Any clue as to how long it will run for ? Depends on how many languages you enabled. In my case: c,c++,fortran,objc Bootstrapping the compilers took about 6 hours, and the testsuite took about 60. Okay, I have just done c, and c++. Have you got testsuite results, have you put them online at all ? Various people run the testsuite on cygwin every now and again; check the gcc-testresults@ mailinglist archive. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Successfull Build of gcc on Cygwin WinXp SP2
Various people run the testsuite on cygwin every now and again; check the gcc-testresults@ mailinglist archive. Yes, Tim has allready run it :- http://gcc.gnu.org/ml/gcc-testresults/2007-04/msg01540.html Aaron -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Successfull Build of gcc on Cygwin WinXp SP2
Aaron Gray wrote: Oh 'make check' is the test suite, did not realize that. I thought it was a separate CVS branch/download. Anyway its been running ten hours now and got to struct-layout-1. Any clue as to how long it will run for ? The last time I built 4.3 (couple of months ago) with all languages including ada and java, it took about 21 hours to bootstrap and 33 hours to run the testsuite. Yes, it just takes forever. Dejagnu forks a ton, and Cygwin is slow at that. However, I have been working on ways of speeding up the dejagnu part. If you copy /usr/bin to a ramdrive, things really take off. Also, removing everything but /usr/bin and %windir%\system32 from $PATH seems to help a little as it prevents stat()-ing around in vein all over the place when spawning. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Successfull Build of gcc on Cygwin WinXp SP2
On 03 May 2007 03:41, Aaron Gray wrote: Various people run the testsuite on cygwin every now and again; check the gcc-testresults@ mailinglist archive. Yes, Tim has allready run it :- http://gcc.gnu.org/ml/gcc-testresults/2007-04/msg01540.html I haven't done one for weeks now http://gcc.gnu.org/ml/gcc-testresults/2007-04/msg00108.html cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Successfull Build of gcc on Cygwin WinXp SP2
Aaron Gray wrote: Any clue as to how long it will run for ? Depends on how many languages you enabled. In my case: c,c++,fortran,objc Bootstrapping the compilers took about 6 hours, and the testsuite took about 60. Okay, I have just done c, and c++. Have you got testsuite results, have you put them online at all ? Yes, but I've not posted them online. My sourcecode was pretty heavily modified so I doubt it will be useful to anyone not working on those specific modifications. -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Successfull Build of gcc on Cygwin WinXp SP2
On 03 May 2007 03:41, Aaron Gray wrote: Various people run the testsuite on cygwin every now and again; check the gcc-testresults@ mailinglist archive. Yes, Tim has allready run it :- http://gcc.gnu.org/ml/gcc-testresults/2007-04/msg01540.html I haven't done one for weeks now Looks like there are some real problems with GCC-4.3-20070427. It fails to compile LLVM on both Cygwin and Linux producing rogue error messages and some weird bugs. Aaron Aaron -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Successfull Build of gcc on Cygwin WinXp SP2
On 01 May 2007 23:48, Brian Dessent wrote: Aaron Gray wrote: Thank you. I am a bit unsure of where abouts (what directory) do you install the snapshot ? Again, this has nothing to do with gcc, take it the Cygwin list. It would be as well to snip the gcc list from the Cc line when giving such advice. that are shared across gcc/binutils/gdb/sim/etc. If you later do cvs up from the toplevel you'll accidently get the entire src tree No, you won't, unless you deliberately add the '-d' option. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Successfull Build of gcc on Cygwin WinXp SP2
Dave Korn wrote: that are shared across gcc/binutils/gdb/sim/etc. If you later do cvs up from the toplevel you'll accidently get the entire src tree No, you won't, unless you deliberately add the '-d' option. Well sure, but then when someone checks in a change that involves renaming or adding a subdirectory somewhere, your tree is silently broken without any warning or indication, and you have to track it down. This can be a lot of head scratching and cursing until you figure out that cvs was too dumb to add the directory to your repository. I prefer to always use cvs up -dP outside of toplevel, which I update with cvs up -lP. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Successfull Build of gcc on Cygwin WinXp SP2
On 02 May 2007 15:59, Brian Dessent wrote: Dave Korn wrote: that are shared across gcc/binutils/gdb/sim/etc. If you later do cvs up from the toplevel you'll accidently get the entire src tree No, you won't, unless you deliberately add the '-d' option. Well sure, but then when someone checks in a change that involves renaming or adding a subdirectory somewhere, your tree is silently broken without any warning or indication, and you have to track it down. If you examine the wording carefully, you can infer that doing cvs up from toplevel without the -d option does not preclude using -d at levels below that This can be a lot of head scratching and cursing until you figure out that cvs was too dumb to add the directory to your repository. Hmmm, I can't think off the top of my head of anything much better than find . -maxdepth 1 -type d | grep -v '\.$' | grep -v CVS | xargs cvs -q -z9 up -dP I prefer to always use cvs up -dP outside of toplevel, which I update with cvs up -lP. I believe the -P option is probably superfluous in that second example! :) cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Successfull Build of gcc on Cygwin WinXp SP2
Dave Korn wrote: If you examine the wording carefully, you can infer that doing cvs up from toplevel without the -d option does not preclude using -d at levels below that Well, depends. I have a line update -dP in my ~/.cvsrc. :-) Hmmm, I can't think off the top of my head of anything much better than find . -maxdepth 1 -type d | grep -v '\.$' | grep -v CVS | xargs cvs -q -z9 up -dP That might be somewhat more efficient than what I use which is set -e echo ./ cvs -q up -lP . for F in `find . -mindepth 1 -maxdepth 1 -type d \! -name CVS`; do echo $F/ cd $F cvs -q up -dP . cd .. done I believe the -P option is probably superfluous in that second example! :) Heh. Well as you can see I tend to use -dP all the time just out of habit. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Successfull Build of gcc on Cygwin WinXp SP2
I have a working GCC-4.3-20070427 on latest Cygwin snapshot. GCC took 8 hours to build ! Thanks alot, Aaron -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Successfull Build of gcc on Cygwin WinXp SP2
On 02 May 2007 13:23, Aaron Gray wrote: I have a working GCC-4.3-20070427 on latest Cygwin snapshot. GCC took 8 hours to build ! g If you think that's slow, try running the full testsuite! Anyway, well done! cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Successfull Build of gcc on Cygwin WinXp SP2
On 02 May 2007 13:23, Aaron Gray wrote: I have a working GCC-4.3-20070427 on latest Cygwin snapshot. GCC took 8 hours to build ! g If you think that's slow, try running the full testsuite! I tried doing 'make check' but it needed autogen which does not build on Cygwin apparently :( I have to get into doing the testsuite soon for another GCC project I am working on, but on Linux, naturally. We have some old dual 500Mhz processor servers I maybe able to get a dual 1GHz too which I am fixing up for the task. Anyway, well done! Thanks, it was all due to the good guidance :) Thanks again, Aaron -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Successfull Build of gcc on Cygwin WinXp SP2
[EMAIL PROTECTED] wrote: On 02 May 2007 13:23, Aaron Gray wrote: I have a working GCC-4.3-20070427 on latest Cygwin snapshot. GCC took 8 hours to build ! g If you think that's slow, try running the full testsuite! I tried doing 'make check' but it needed autogen which does not build on Cygwin apparently :( autoconf, automake, dejagnu, expect, tcltk should be enough to run testsuite, once you have built gcc. Unlike typical linux, stock cygwin builds of the utilities are sufficient. If testsuite looks for autogen, it means something else is broken. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Successfull Build of gcc on Cygwin WinXp SP2
On 02 May 2007 14:10, Aaron Gray wrote: On 02 May 2007 13:23, Aaron Gray wrote: I have a working GCC-4.3-20070427 on latest Cygwin snapshot. GCC took 8 hours to build ! g If you think that's slow, try running the full testsuite! I tried doing 'make check' but it needed autogen which does not build on Cygwin apparently :( That's just the fixincludes tests, and the failure causes make to exit. Use make -k check. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Successfull Build of gcc on Cygwin WinXp SP2
Aaron Gray wrote: I tried doing 'make check' but it needed autogen which does not build on Cygwin apparently :( That's just the fixincludes dir. It's not important. This is why the instructions tell you to run make -k check. And autogen does build on Cygwin. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Successfull Build of gcc on Cygwin WinXp SP2
Aaron Gray wrote: I tried doing 'make check' but it needed autogen which does not build on Cygwin apparently :( That's just the fixincludes dir. It's not important. This is why the instructions tell you to run make -k check. Okay I will try that. And autogen does build on Cygwin. Right I just read it in a posting I got from Google. I stand corrected. Aaron -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Successfull Build of gcc on Cygwin WinXp SP2
Aaron Gray wrote: Thank you. I am a bit unsure of where abouts (what directory) do you install the snapshot ? Again, this has nothing to do with gcc, take it the Cygwin list. If you are using the full snapshots (cygwin-inst-$date.tar.bz2) they should be unpacked in the root (/). The other types are just the cygwin1.dll which goes in /usr/bin of course. And again, you do *not* need to mess with any of this to make stdio.h usable for building gcc. Just take stdio.h from newlib HEAD and place it in /usr/include. The FAQ does not seem to say that. From the instructions it would seem it would go in the current users directory. Read it again. Both tar commands include -C which means cd to this directory before extacting. I am a bit confused what winsup is as well. That is just a directory in the src tree that contains the code for Cygwin, MinGW, w32api, and other miscellaneous Windows things. But note that you can't build Cygwin from just winsup/cygwin, as Cygwin needs other parts of the src tree, such as libiberty and newlib. When you do a cvs co cygwin that is actually a CVS module that gets you a selected subset of the entire src tree, including the toplevel scripts that are shared across gcc/binutils/gdb/sim/etc. If you later do cvs up from the toplevel you'll accidently get the entire src tree which you don't need, so you have to do cvs up in each individual directory. Thanks. I think I understand most of that and will try again fresh tommorow. I'll try not to bother the GCC list if I can possibly avoid it. Thanks again, Aaron -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
