Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
	        Charles Wilson <cygwin@cwilson.fastmail.fm>,
	        Nick Clifton <nickc@redhat.com>,
	gcc-patches@gcc.gnu.org,         gdb-patches@sourceware.org,
	binutils@sourceware.org
Subject: Re: RFA/RFC: Pass --cache-file=/dev/null on to subconfigures
Date: Fri, 25 Sep 2009 19:31:00 -0000	[thread overview]
Message-ID: <4ABD1A72.8080203@redhat.com> (raw)
In-Reply-To: <20090925172108.GA1808@gmx.de>

Hi Ralf,

> Please do commit it, since I guess it is necessary in practice.

Done.

> However, this necessity is always a sign of a bug in the GCC/src
> build system.

True.

> Well, with upstream Autoconf, you only ever have one cache file anyway,
> so it works there.

Really ?  I did not realise that.

> GCC/src could easily let such a switch cause the
> use of different cache file names in the sub-directories.  I'm not sure
> what the benefit would be, though.

Nor do I.  It was more of a theoretical situation than anything I might 
actually expect to happen in real life.

Cheers
   Nick



  parent reply	other threads:[~2009-09-25 19:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-25 10:24 Nick Clifton
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 [this message]
     [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=4ABD1A72.8080203@redhat.com \
    --to=nickc@redhat.com \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=binutils@sourceware.org \
    --cc=cygwin@cwilson.fastmail.fm \
    --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