unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: bug-guile@gnu.org
Subject: [PATCH] Save config.cache before tests which are likely to fail.
Date: Sat, 12 Feb 2011 10:56:20 +0100	[thread overview]
Message-ID: <20110212095619.GB3799@gmx.de> (raw)

Guile's configure script takes fairly long.  On a system without
automatic build dependency installation, it is amplified by the fact
that your user might be both impatient and not read the build
instructions, thus needs to rerun configure several times only to find
out there is another dependency to install.  Still, there is help even
for such kinds of misguided figures such as me: save the temporary
config.cache file (if one is used anyway) before embarking upon the set
of tests that are likely to error out.  That way, the second and further
reruns are much faster.

The downside of this patch is that, when fixing the errors requires
changing to precious variables (such as CPPFLAGS or so), the user will
need to 'rm -f config.cache' to keep configure happy.

* configure.ac: Call AC_CACHE_SAVE before the gmp tests.
---

Hello,

Which alternative do you prefer?
See 'info Autoconf --index AC_CACHE_SAVE' for more information.

Thanks for maintaining guile,
Ralf

 configure.ac |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/configure.ac b/configure.ac
index 69f35e2..2cd8b4d 100644
--- a/configure.ac
+++ b/configure.ac
@@ -855,6 +855,7 @@ main (void)
   esac
 fi
 
+AC_CACHE_SAVE
 
 dnl GMP tests
 AC_LIB_HAVE_LINKFLAGS([gmp],
-- 
1.7.4.1.gd5c55



             reply	other threads:[~2011-02-12  9:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-12  9:56 Ralf Wildenhues [this message]
2011-02-12 11:05 ` [PATCH] Save config.cache before tests which are likely to fail Andy Wingo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110212095619.GB3799@gmx.de \
    --to=ralf.wildenhues@gmx.de \
    --cc=bug-guile@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).