This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: Runtime for "make check-fortran" on Cygwin? What's typical?
- From: Tim Prince <timothyprince at sbcglobal dot net>
- To: Brooks Moses <brooks dot moses at codesourcery dot com>
- Cc: fortran at gcc dot gnu dot org
- Date: Sat, 04 Nov 2006 11:56:30 -0800
- Subject: Re: Runtime for "make check-fortran" on Cygwin? What's typical?
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=4wpeTgEx0ao6O57zkmGwnteLGmXs3oAravUp1dz9Q4erl0fkyFN+CZzzWZ7vynVJcV8XSLdNX6rIlpXQPqcHEBQPi1GVnyii/UeeQFVDA8Jp6DsGbdi9/soPXjZaChavl5u0QRK3uXxoSg6HZWpaLAtnmPK2qfZL8Sn/lqhXNKw= ;
- References: <4.3.1.2.20061103003052.029eaf00@cits1.stanford.edu>
- Reply-to: tprince at myrealbox dot com
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.