From: DJ Delorie <dj@delorie.com>
To: aoliva@redhat.com
Cc: drow@mvista.com, gcc-patches@gcc.gnu.org,
gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: (toplevel) Fix dramatic breakage for ordinary crosses (related to program_transform_name)
Date: Sat, 28 Dec 2002 14:14:00 -0000 [thread overview]
Message-ID: <200212282151.gBSLp4Z09145@envy.delorie.com> (raw)
In-Reply-To: <oradip51r7.fsf@free.redhat.lsd.ic.unicamp.br> (message from Alexandre Oliva on 28 Dec 2002 18:26:04 -0200)
> Why not? It's just a cache, after all! Worst case, when you
> reconfigure, you get to rerun some tests. So what?
Worst case is config.cache gets corrupt values, and the build breaks.
I agree it's rare. If we understand the risk, and collectively decide
to live with it until an actual problem happens, I'm OK with that.
> > But it would be nice if autoconf managed this problem for us.
>
> It can't. Consider that the config.cache file specified in the
> command line may be in a directory that is not writable,
That's a different type of problem. Does autoconf allow for failure
to write to config.cache?
next prev parent reply other threads:[~2002-12-28 21:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-28 4:36 Nathanael Nerode
2002-12-28 8:33 ` Alexandre Oliva
2002-12-28 9:51 ` Daniel Jacobowitz
2002-12-28 9:56 ` Alexandre Oliva
2002-12-28 9:59 ` Daniel Jacobowitz
2002-12-28 10:41 ` Alexandre Oliva
2002-12-28 10:46 ` Dan Kegel
2002-12-28 11:07 ` DJ Delorie
2002-12-28 12:26 ` Daniel Jacobowitz
2002-12-28 10:50 ` Daniel Jacobowitz
2002-12-28 11:01 ` DJ Delorie
2002-12-28 12:57 ` Alexandre Oliva
2002-12-28 13:51 ` Alexandre Oliva
2002-12-29 18:57 ` Alexandre Oliva
2002-12-28 14:14 ` DJ Delorie [this message]
2002-12-28 15:22 ` Alexandre Oliva
2002-12-28 10:54 ` Alexandre Oliva
2002-12-28 10:49 ` DJ Delorie
2002-12-28 11:00 ` DJ Delorie
-- strict thread matches above, loose matches on Subject: below --
2003-01-06 0:49 Michael Elizabeth Chastain
2002-12-29 0:39 Michael Elizabeth Chastain
2002-12-29 2:48 ` Alexandre Oliva
2002-12-28 13:22 Michael Elizabeth Chastain
2002-12-28 13:44 ` Alexandre Oliva
2003-01-06 0:04 ` Ben Elliston
2002-12-28 1:00 Nathanael Nerode
2002-12-28 1:22 ` Alexandre Oliva
2002-12-28 1:33 ` Alexandre Oliva
2002-12-28 7:47 ` Kazu Hirata
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=200212282151.gBSLp4Z09145@envy.delorie.com \
--to=dj@delorie.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=drow@mvista.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.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