Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org,
	        gcc-patches@gcc.gnu.org
Subject: Re: Remove config.cache files when reconfiguring at top level
Date: Tue, 16 Feb 2010 10:07:00 -0000	[thread overview]
Message-ID: <4B7A6E32.6070307@redhat.com> (raw)
In-Reply-To: <m2k4ue2x62.fsf@igel.home>

Hi Andreas,

>> Ah - I did not know that users would ever modify the cache files.
>
> That's the only way to override cross-compile defaults in target
> libraries.

Hmm, I feel that there ought to be a better way to do that, but OK.

I would like to make the command line option to preserve the 
config.cache files opt-in, (ie the files are deleted unless this option 
is enabled as the configure script is run).  The reason being that I 
think that most users would expect a:

   configure <new-flags>
   make distclean
   make

sequence to just work without needing any extra configure options.  So I 
would propose adding a:

   --preserve-caches

option.  Is that OK with you ?

Cheers
   Nick



  parent reply	other threads:[~2010-02-16 10:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15 10:53 Nick Clifton
2010-02-15 10:58 ` Andreas Schwab
2010-02-15 15:54   ` Nick Clifton
2010-02-15 18:04     ` Andreas Schwab
2010-02-15 18:23       ` Alfred M. Szmidt
2010-02-15 19:37         ` Andreas Schwab
2010-02-16 11:23           ` Alfred M. Szmidt
2010-02-16 10:07       ` Nick Clifton [this message]
     [not found]       ` <4B7A6E32.6070307__49868.1737961762$1266314832$gmane$org@redhat.com>
2010-02-16 10:42         ` Andreas Schwab
2010-02-16 11:04           ` Nick Clifton
2010-02-16 11:12             ` Andreas Schwab
2010-02-16 11:23             ` Alfred M. Szmidt
2010-02-16 12:40               ` Nick Clifton
2010-02-16 13:25                 ` Alfred M. Szmidt
2010-02-16 14:03                   ` Andreas Schwab
2010-02-17 10:06                   ` Nick Clifton
2010-02-17 10:17                     ` Mark Kettenis
2010-02-17 11:04                       ` Nick Clifton

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=4B7A6E32.6070307@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=schwab@linux-m68k.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