From: DJ Delorie <dj@redhat.com>
To: aoliva@redhat.com
Cc: drow@mvista.com, gcc@gcc.gnu.org, neroden@gcc.gnu.org
Subject: Re: Serialization dependencies muck up configure-on-demand
Date: Mon, 23 Dec 2002 15:07:00 -0000 [thread overview]
Message-ID: <200212232134.gBNLYOu07414@greed.delorie.com> (raw)
In-Reply-To: <orznqwzapr.fsf@free.redhat.lsd.ic.unicamp.br> (message from Alexandre Oliva on 23 Dec 2002 19:28:32 -0200)
> We can use shell locking (*) in the top level to make sure no two
> configures run at the same time, if we really need that.
I really don't want to create a spinlock system just for a build.
There are too many weird ways that can fail.
> Serialized dependencies are exactly the wrong way to solve the
> problem, IMO. I hadn't realized they had been implemented like
> that, otherwise I'd have objected.
We've done it before. We're using the "can't do this until you do
that" half of the dependency logic, not the "I need this built for my
build" half.
next prev parent reply other threads:[~2002-12-23 21:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-23 11:36 Daniel Jacobowitz
2002-12-23 12:39 ` DJ Delorie
2002-12-23 12:40 ` Daniel Jacobowitz
2002-12-23 13:46 ` DJ Delorie
2002-12-23 14:37 ` Alexandre Oliva
2002-12-23 15:07 ` DJ Delorie [this message]
2002-12-26 1:38 ` Alexandre Oliva
2002-12-26 6:53 ` DJ Delorie
2002-12-23 13:25 Nathanael Nerode
2002-12-23 13:36 ` Daniel Jacobowitz
2002-12-24 15:42 ` Paul D. Smith
2002-12-23 13:28 Nathanael Nerode
2002-12-23 13:34 ` Daniel Jacobowitz
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=200212232134.gBNLYOu07414@greed.delorie.com \
--to=dj@redhat.com \
--cc=aoliva@redhat.com \
--cc=drow@mvista.com \
--cc=gcc@gcc.gnu.org \
--cc=neroden@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).