This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: sqlite defect
- From: jojelino <jojelino at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 19 Jul 2013 21:36:07 +0900
- Subject: Re: sqlite defect
- References: <trinity-1068d666-3dec-43c9-8453-39c7cae3a94c-1374102947415 at 3capp-gmx-bs33> <51E74AB4 dot 7010508 at etr-usa dot com> <ks87ur$nle$1 at ger dot gmane dot org> <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>
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.
--
Regards.
--
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