X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 17 Apr 2009 15:31:03 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [1.7] flock change breaks autotools 'make -j2' Message-ID: <20090417133103.GG8722@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20090417100148 DOT GD5200 AT calimero DOT vinschen DOT de> <49E87CFA DOT 9070709 AT byu DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49E87CFA.9070709@byu.net> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Apr 17 06:58, Eric Blake wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > According to Corinna Vinschen on 4/17/2009 4:01 AM: > > Default question: Do you have a simple testcase to reproduce this > > problem? I'm going to play with the lock.pl perl script from > > http://lists.gnu.org/archive/html/bug-automake/2009-04/msg00053.html but > > I don't know if I can get it working. Perl isn't exactly my domain. > > I'd prefer a testcase in C. > > So would I. I'm not even sure whether perl was using flock or > lockf/fcntl. Do you still need me to try and write a STC, or at least > test how perl behaves with your first patch? I checked in a patch which hopefully solves both problems. The lock.pl testcase now works, at least. Can you test if the original scenario works now as well? If not, I'd really need another testcase. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/