This is the mail archive of the
mailing list for the cygwin project.
questions on ./configure
- From: Carlo Florendo <list-subscriber at hq dot astra dot ph>
- To: cygwin-talk at cygwin dot com
- Date: Mon, 16 May 2005 17:14:52 +0800
- Subject: questions on ./configure
- Reply-to: Talk Amongst Yourselves <cygwin-talk at cygwin dot com>
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?
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
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
Astra Philippines Inc.