From: Andreas Schwab <schwab@linux-m68k.org>
To: ams@gnu.org
Cc: nickc@redhat.com, binutils@sourceware.org,
gdb-patches@sourceware.org, gcc-patches@gcc.gnu.org
Subject: Re: Remove config.cache files when reconfiguring at top level
Date: Mon, 15 Feb 2010 19:37:00 -0000 [thread overview]
Message-ID: <m2fx522sui.fsf@igel.home> (raw)
In-Reply-To: <E1Nh5bC-0003QR-AO@fencepost.gnu.org> (Alfred M. Szmidt's message of "Mon, 15 Feb 2010 13:23:10 -0500")
"Alfred M. Szmidt" <ams@gnu.org> writes:
> >> This should be optional, as it also erases any manual changes
> >> added to the cache file.
> >
> > 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.
>
> Can't you pass the variables on the command line? I.e.
>
> .../configure ac_cv_foo=123
That would also pass it to the host libraries, where it may be
inappropriate.
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:[~2010-02-15 19:37 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 [this message]
2010-02-16 11:23 ` Alfred M. Szmidt
2010-02-16 10:07 ` Nick Clifton
[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=m2fx522sui.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=ams@gnu.org \
--cc=binutils@sourceware.org \
--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