From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-65250-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 6445 invoked by alias); 25 Dec 2002 05:29:44 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 6434 invoked from network); 25 Dec 2002 05:29:43 -0000
Received: from unknown (HELO mx1.redhat.com) (66.187.233.31)
  by 209.249.29.67 with SMTP; 25 Dec 2002 05:29:43 -0000
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254])
	by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id gBP52mB17742;
	Wed, 25 Dec 2002 00:02:48 -0500
Received: from post-office.corp.redhat.com (post-office.corp.redhat.com [172.16.52.227])
	by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id gBP5TUa00839;
	Wed, 25 Dec 2002 00:29:30 -0500
Received: from greed.delorie.com (dj.cipe.redhat.com [10.0.0.222])
	by post-office.corp.redhat.com (8.11.6/8.11.6) with ESMTP id gBP5TTK10284;
	Wed, 25 Dec 2002 00:29:29 -0500
Received: (from dj@localhost)
	by greed.delorie.com (8.11.6/8.11.6) id gBP5TSP04337;
	Wed, 25 Dec 2002 00:29:28 -0500
Date: Thu, 26 Dec 2002 06:53:00 -0000
Message-Id: <200212250529.gBP5TSP04337@greed.delorie.com>
From: DJ Delorie <dj@redhat.com>
To: aoliva@redhat.com
CC: drow@mvista.com, gcc@gcc.gnu.org, neroden@gcc.gnu.org
In-reply-to: <or4r9226an.fsf@free.redhat.lsd.ic.unicamp.br> (message from
	Alexandre Oliva on 25 Dec 2002 00:14:56 -0200)
Subject: Re: Serialization dependencies muck up configure-on-demand
References: <20021223182335.GA17240@nevyn.them.org>
	<200212231833.gBNIX4o14365@greed.delorie.com>
	<orznqwzapr.fsf@free.redhat.lsd.ic.unicamp.br>
	<200212232134.gBNLYOu07414@greed.delorie.com> <or4r9226an.fsf@free.redhat.lsd.ic.unicamp.br>
X-SW-Source: 2002-12/txt/msg01424.txt.bz2


> If you print a message saying `waiting for [lockdir] to go away...'
> before sleeping, the user will probably be able to figure it out if
> something goes wrong. 

Unless your cron job mysteriously runs forever...