Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
	        binutils@sourceware.org
Subject: RFA/RFC: Pass --cache-file=/dev/null on to subconfigures
Date: Fri, 25 Sep 2009 10:24:00 -0000	[thread overview]
Message-ID: <m3ljk31fwr.fsf@redhat.com> (raw)

Hi Guys,

  I am regularly encountering problems rebuilding my toolchains
  because the config.cache file in one or more of the sub-directories
  is inconsistent:

configure: error: run `make distclean' and/or `rm ./config.cache' and start over
  
  This is annoying because it stops the automated build process and I
  have to manually remove the cache file before I can resume it.
  Since I am not worried about the time it takes to rerun the
  configure script in these sub-directories I would like to be able to
  build the entire toolchain without using any caches.

  In theory I can specify "--cache-file=/dev/null" when configuring
  the toolchain.  Unfortunately the top level configure file strips
  out all --cache-file arguments before invoking configure in any of
  the sub-directories.  Although this might be reasonable for a
  configure cache that is specified via an absolute path, it is
  unreasonable when the user is trying to disable caches altogether.

  So I have created the patch below.  It simply allows
  --cache-file=/dev/null to be passed on to the configure scripts in
  the sub-directories.  I have run a gcc bootstrap without problems
  and so I would like to apply the patch.

  Any comments or reasons why the patch should not be applied ?

Cheers
  Nick

./ChangeLog
2009-09-25  Nick Clifton  <nickc@redhat.com>

	* configure.ac: Pass any --cache-file=/dev/null option on to
	subconfigures.
	* configure: Regenerate.

Index: configure.ac
===================================================================
--- configure.ac	(revision 152111)
+++ configure.ac	(working copy)
@@ -2632,9 +2632,11 @@
 
 # Base args.  Strip norecursion, cache-file, srcdir, host, build,
 # target, nonopt, and variable assignments.  These are the ones we
-# might not want to pass down to subconfigures.  Also strip
-# program-prefix, program-suffix, and program-transform-name, so that
-# we can pass down a consistent program-transform-name.
+# might not want to pass down to subconfigures.  The exception being
+# --cache-file=/dev/null, which is used to turn off the use of cache
+# files altogether, and which should be passed on to subconfigures.
+# Also strip program-prefix, program-suffix, and program-transform-name,
+# so that we can pass down a consistent program-transform-name.
 baseargs=
 keep_next=no
 skip_next=no
@@ -2673,6 +2675,13 @@
   esac
 
   case "$ac_arg" in
+    --cache-file=/dev/null | \
+    -cache-file=/dev/null )
+      # Handled here to avoid the test to skip args below.
+      baseargs="$baseargs '$ac_arg'"
+      # Assert: $separate_arg should always be no.
+      keep_next=$separate_arg
+      ;;
     --no*)
       continue
       ;;


             reply	other threads:[~2009-09-25 10:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-25 10:24 Nick Clifton [this message]
2009-09-25 11:06 ` Ralf Wildenhues
2009-09-25 14:50   ` Nick Clifton
     [not found] ` <20090925110629.GA25946__23064.0259491794$1253876825$gmane$org@ins.uni-bonn.de>
2009-09-25 14:49   ` Charles Wilson
2009-09-25 17:21     ` Ralf Wildenhues
2009-09-25 17:29       ` DJ Delorie
2009-09-25 17:48         ` Ralf Wildenhues
2009-09-25 18:06       ` Charles Wilson
2009-09-25 19:31       ` Nick Clifton
     [not found]   ` <4ABCD858.3030400__7010.59009084037$1253890491$gmane$org@cwilson.fastmail.fm>
2009-09-25 17:13     ` Andreas Schwab
2009-09-25 18:02       ` Charles Wilson

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

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

  git send-email \
    --in-reply-to=m3ljk31fwr.fsf@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.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