Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top


$ ./configure
configure: configuring for GNU Wget 1.11
checking build system type... i686-apple-darwin10.0.0
checking host system type... i686-apple-darwin10.0.0
checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for gcc... gcc

Is there a way to skip the "checking.." messages when running configure? I know the checks are there for a reason, but when wanting to quickly compile something, it's a pain to have to wait while configure is "checking for AIX" or if the compiler supports the long data-type.. I guess not, since the checks are probably used to determine paths for gcc etc etc..

I know you can silence the messages with --quiet but this is not what I'm looking for,

  -q, --quiet, --silent   do not print `checking...' messages
share|improve this question
So, in a nutshell, you're in a hurry and you want the machine to build the software for you without any idea of the specifications it should build towards? Sounds like a good idea to me... – Telemachus Aug 31 '09 at 0:15
up vote 4 down vote accepted

./configure can be told to cache the results of the checks with the option -C, see here.

share|improve this answer

autoconf is used to provide a way of determining the capabilities of the host on which the application is being compiled. Skipping these checks would imply it doesn't know what the capabilities of the build target.

As mentioned above, you can cache the results but you'd need to run it at least once to prime the cache.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.