From: Andreas Schwab <schwab@linux-m68k.org>
To: Charles Wilson <cygwin@cwilson.fastmail.fm>
Cc: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
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 17:13:00 -0000 [thread overview]
Message-ID: <m2pr9f3q3l.fsf@igel.home> (raw)
In-Reply-To: <4ABCD858.3030400__7010.59009084037$1253890491$gmane$org@cwilson.fastmail.fm> (Charles Wilson's message of "Fri, 25 Sep 2009 10:48:56 -0400")
Charles Wilson <cygwin@cwilson.fastmail.fm> writes:
> I've seen it happen -- building gdb/insight which is part of the src
> tree if not gcc specfically -- when a precious variable contained a
> leading space. I think it was because the top-level configure
> automatically augmented it as follows, when the var was originally empty:
>
> X="$X --some-new-flag"
>
> For some reason, the sub-configure had the variable without the leading
> space, so it complained of a mismatch.
That should no longer be an issue with the switch to autoconf 2.64.
Such whitespace differences are now ignored.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2009-09-25 17:13 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
[not found] ` <4ABCD858.3030400__7010.59009084037$1253890491$gmane$org@cwilson.fastmail.fm>
2009-09-25 17:13 ` Andreas Schwab [this message]
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=m2pr9f3q3l.fsf@igel.home \
--to=schwab@linux-m68k.org \
--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 \
--cc=nickc@redhat.com \
/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