From: Daniel Jacobowitz <drow@mvista.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Nathanael Nerode <neroden@twcny.rr.com>,
gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
binutils@sources.redhat.com, dj@redhat.com, autoconf@gnu.org
Subject: Re: (toplevel) introduce host subdir configuration in Makefile
Date: Mon, 02 Dec 2002 10:23:00 -0000 [thread overview]
Message-ID: <20021202182338.GA16046@nevyn.them.org> (raw)
In-Reply-To: <orvg2cl3ii.fsf@free.redhat.lsd.ic.unicamp.br>
On Mon, Dec 02, 2002 at 03:44:21PM -0200, Alexandre Oliva wrote:
> One way to try to overcome this limitation in autoconf that has just
> occurred to me is to offload the updating of a shared config.cache to
> the top-level Makefile. E.g., the Makefile safely copies the
> top-level config.cache to a subdirectory before it configures it, and
> safely copies it back (or merges it) with the top-level config.cache
> when configure finishes. Safety can be accomplished with
>
> cp ${cache_file} subdir/config.cache
> run configure in subdir, with --config-cache=./config.cache
> mv subdir/config.cache ${cache_file}
>
> trying to merge the contents can get trickier, but I believe it can be
> done too.
>
> The one thing we'd have to be careful about is in case the user
> specified a config.cache to the top-level, especially /dev/null. We
> may have to handle that especially, like autoconf does.
Yeah, I think this would be the way to go; but in any case, I suggest
that we serialize configure targets if it's practical to do so.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-12-02 18:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 14:13 Nathanael Nerode
2002-11-29 8:44 ` Andrew Cagney
2002-12-02 8:18 ` Daniel Jacobowitz
2002-12-02 8:40 ` Alexandre Oliva
2002-12-02 8:52 ` Daniel Jacobowitz
2002-12-02 9:44 ` Alexandre Oliva
2002-12-02 10:23 ` Daniel Jacobowitz [this message]
2002-12-02 12:48 ` Alexandre Oliva
2002-12-02 13:43 ` DJ Delorie
2002-12-02 14:03 ` Thomas Dickey
2002-12-04 0:42 ` Samuel Tardieu
2002-12-04 3:14 ` Thomas E. Dickey
2002-12-02 10:17 ` DJ Delorie
2002-11-29 13:51 Nathanael Nerode
2002-11-29 14:23 ` Andrew Cagney
2002-11-29 14:40 Nathanael Nerode
2002-11-29 15:16 ` Andrew Cagney
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=20021202182338.GA16046@nevyn.them.org \
--to=drow@mvista.com \
--cc=aoliva@redhat.com \
--cc=autoconf@gnu.org \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@twcny.rr.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