questions on ./configure

[Carlo Florendo]

Hello,

Everyone knows that running ./configure when starting to build a 
software may take some time.  Does anyone know how to re-run ./configure 
such  that it skips the part that has been tested before?

For example, the following configure output is taken from trying to 
configure coreutils for cygwin.    I believe the following checks could 
be skipped, right?  If so, how is it done?

administrator@garden /tmp/coreutils-5.3.0
$ ./configure     
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for desired default level of POSIX conformance... none-specified
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.exe
<snipped>
.
.
.
<continued>
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes


Thanks!

Best Regards,

Carlo

-- 
Carlo Florendo
Astra Philippines Inc.
www.astra.ph