Serialization dependencies muck up configure-on-demand

[Alexandre Oliva]

On Dec 23, 2002, DJ Delorie <dj@redhat.com> wrote:

>> 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.

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.  And things will only go wrong if the user
actually aborts some running configure, which has always been a bad
idea anyway (especially when started from ./config.status --recheck).

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer