www.delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-3.2 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_52,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS |
X-Spam-Check-By: | sourceware.org |
To: | cygwin AT cygwin DOT com |
From: | Eric Blake <ebb9 AT byu DOT net> |
Subject: | [1.7] flock change breaks autotools 'make -j2' |
Date: | Thu, 16 Apr 2009 20:39:12 +0000 (UTC) |
Lines: | 24 |
Message-ID: | <loom.20090416T201917-225@post.gmane.org> |
Mime-Version: | 1.0 |
User-Agent: | Loom/3.14 (http://gmane.org/) |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
This change in cygwin 1.7: - File locking is now advisory, not mandatory anymore. The fcntl(2) and the new lockf(2) APIs create and maintain locks with POSIX semantics, the flock(2) API creates and maintains locks with BSD semantics. POSIX and BSD locks are independent of each other. is causing parallel make bugs in autotooled projects: http://lists.gnu.org/archive/html/bug-automake/2009-04/msg00048.html The problem is that perl's flock is no longer locking files the way it used to, so parallel instances of autom4te (the engine behind both autoconf and automake) end up stomping on each others' output. I don't know if it something that needs to be fixed in perl, in automake's XFile::lock wrapper around perl's flock, or even in cygwin itself. But it seems like if two instances of the same perl program are using the same advisory locking mechanism, that they should keep each other out of the file properly (advisory means that processes not using flock can still stomp on the file, but not other processes using the same locking mechanism). -- Eric Blake -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |