Runtime for "make check-fortran" on Cygwin? What's typical?

Tim Prince timothyprince@sbcglobal.net
Sat Nov 4 19:56:00 GMT 2006


Brooks Moses wrote:
> So, I finally got dejagnu worked out to run properly on my Cygwin 
> installation.  (The relevant incantation seemed to be "setenv 
> DEJAGNULIBS /usr/share/dejagnu", to fix an error of "couldn't find 
> runtext.exp")  And so I did a run of "make check-fortran", to make sure 
> it was working, and get a baseline before making changes.
> 
> Eight hours later, I think it's almost done.  Most of the time, it 
> hasn't been using the CPU much at all, but the disk is working away.
> 
> Is this normal for Cygwin?  How long does a "make check-fortran" run 
> usually take?  What about on non-Cygwin machines?
> 
Installing dejagnu and friends from the cygwin setup should be 
sufficient to take care of those problems.
I generally do make check for C and C++ as well as Fortran, as I see no 
chance of gfortran making the cygwin distribution without the others. 
All this takes about 2 days on my pentium-m laptop, maybe 5 hours for 
the Fortran part.  It used to be much faster, prior to "upgrades" of 
BIOS, Windows, and cygwin, but it always took twice as long as linux.



More information about the Fortran mailing list