X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=Ou8g4AZy+H/ouZrqr/LD+SJkpjdzxvodBZnN1hWR8bv2v/NJ4dNwU
	bWZivdWuifo6qICNm/FZaQETQgNwY/NoxuzYy6QeBqwebiLgMd2n5kEW9vCyZHS9
	5zcCGLUGzKDOnKcMMPhUuZdtUgIIL26uPmQVRAPNpHmLpbc/eDKch4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=4vEPSn4NGTSpFys3+sqNI09p580=; b=uB/4I5oc7XsezB79Psrum86b5r/r
	STk0D68HZo+ajwqjiLbCLab4kgX0rKJGOE2oKtj+rvYDnp9my1QiYIeX+dJK7ZFC
	ch95nRh6G7fswibxihqcb2M4ZJgvjghi5kydtjyc4J1mj9cJNYwGIdkS4JDoc9mG
	rXrwCQHewR7y6sE=
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
X-Spam-SWARE-Status: No, score=0.1 required=5.0 tests=AWL,BAYES_50,RDNS_NONE autolearn=no version=3.3.1
Date: Fri, 19 Jul 2013 14:57:29 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: sqlite defect
Message-ID: <20130719125729.GA883@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20130718085953 DOT GC9628 AT calimero DOT vinschen DOT de> <ksa6bs$ac9$1 AT ger DOT gmane DOT org> <20130719100329 DOT GC20871 AT calimero DOT vinschen DOT de> <20130719100809 DOT GD20871 AT calimero DOT vinschen DOT de> <ksb4cn$cp8$1 AT ger DOT gmane DOT org> <20130719113009 DOT GE20871 AT calimero DOT vinschen DOT de> <ksb9be$2ss$1 AT ger DOT gmane DOT org> <20130719120242 DOT GH20871 AT calimero DOT vinschen DOT de> <ksba88$bvs$1 AT ger DOT gmane DOT org> <ksbbrk$ts4$1 AT ger DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <ksbbrk$ts4$1@ger.gmane.org>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Jul 19 21:36, jojelino wrote:
> On 2013-07-19 PM 9:08, jojelino wrote:
> >On 2013-07-19 PM 9:02, Corinna Vinschen wrote:
> >>There *is* a workaround:
> >>
> >>   export CYGWIN_SQLITE_LOCKING=posix
> >>
> >>See http://cygwin.com/ml/cygwin-announce/2013-06/msg00014.html
> >>
> >It's very good workaround instead of rebuild sqlite3. thanks for the point.
> Also, I commented out F_LCK_MANDATORY in fcntl.h to keep from
> confronting the disastrous situation introduced by this experimental
> feature. I expect it would save many hours instead of digging into
> unmaintained source codes. especially for projects that uses the
> sort of autotools which just checks the existence of F_LCK_MANDATORY
> macro. and is optimistic about the experimental feature.

This is over the top.  F_LCK_MANDATORY is a Cygwin invention not known
to the outer world, *and* the behaviour of F_LCK_MANDATORY is
documented.  If any project actually chooses to use it, it will do so
with the full information about the semantics given.  Also, since
mandatory locking is not standard conformant anyway, the project
has to know exactly what it's doing.  So what's your point?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple