This is the mail archive of the
cygwin-talk@cygwin.com
mailing list for the cygwin project.
Re: questions on ./configure
On Wed, May 18, 2005 at 08:48:02AM +0800, Carlo Florendo wrote:
>Christopher Faylor wrote:
>>On Mon, May 16, 2005 at 05:14:52PM +0800, Carlo Florendo wrote:
>>>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?
>>
>>You know, I knew it would happen eventually. You're using this list
>>because you apparently can't be bothered to read documentation or find
>>an appropriate mailing list for your questions.
>>
>Yup, http://cygwin.com/lists.html
>
>This list is nice. I try to look for what's needed and if I can't find
>it, I try it out here.
If you think that the cygwin-talk list is really the best place to get
autoconf questions answered after reading lists.html then I guess that
explains why you're having difficulty.
However, since you do seem to understand the basic mean help +
entertainment concept I guess I have to cut you some slack.
><config snippet>
>Some influential environment variables:
> DEFAULT_POSIX2_VERSION
> POSIX version to default to; see 'config.hin'.
> CC C compiler command
> CFLAGS C compiler flags
> LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
> nonstandard directory <lib dir>
> CPPFLAGS C/C++ preprocessor flags, e.g. -I<include dir> if you have
> headers in a nonstandard directory <include dir>
> CPP C preprocessor
></config snippet>
>
>However, it's not indicative of what to disable. For example, how do
>you prevent checks for the following:
I guess some configure's differ in what they display. You'll have to
keep reading apparently all the way up to the "--cache-file" option.
cgf