This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: RFA/RFC: Pass --cache-file=/dev/null on to subconfigures
- From: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
- To: Andreas Schwab <schwab at linux-m68k dot org>
- Cc: Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>, Nick Clifton <nickc at redhat dot com>, gcc-patches at gcc dot gnu dot org, gdb-patches at sourceware dot org, binutils at sourceware dot org
- Date: Fri, 25 Sep 2009 14:02:30 -0400
- Subject: Re: RFA/RFC: Pass --cache-file=/dev/null on to subconfigures
- References: <m3ljk31fwr.fsf@redhat.com> <20090925110629.GA25946__23064.0259491794$1253876825$gmane$org@ins.uni-bonn.de> <4ABCD858.3030400__7010.59009084037$1253890491$gmane$org@cwilson.fastmail.fm> <m2pr9f3q3l.fsf@igel.home>
Andreas Schwab wrote:
> 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.
Ah:
$ find . -name "configure"|\
xargs grep 'Generated by GNU Autoconf' | grep -v 2.64
./gdb/gdbtk/configure:# Generated by GNU Autoconf 2.59.
./gdb/gdbtk/plugins/configure:# Generated by GNU Autoconf 2.59.
./gdb/testsuite/gdb.cell/configure:# Generated by GNU Autoconf 2.59.
./gdb/testsuite/gdb.gdbtk/configure:# Generated by GNU Autoconf 2.59.
./libgui/configure:# Generated by GNU Autoconf 2.59.
Looks like some stuff missed regeneration?
--
Chuck