X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,FSL_HELO_BARE_IP_2,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Achim Gratz Subject: Re: Promote sqlite 3.7.13-1 from test status? Date: Fri, 1 Mar 2013 15:11:55 +0000 (UTC) Lines: 29 Message-ID: References: <502C0B7D DOT 10909 AT etr-usa DOT com> <20120816085016 DOT GB5536 AT calimero DOT vinschen DOT de> <502CCBB1 DOT 2070600 AT etr-usa DOT com> <20120816105507 DOT GD17546 AT calimero DOT vinschen DOT de> <502CE120 DOT 4050900 AT etr-usa DOT com> <20120816122654 DOT GG17546 AT calimero DOT vinschen DOT de> <502D1967 DOT 7090705 AT etr-usa DOT com> <20120816160656 DOT M21257 AT ds DOT net> <502D3A5C DOT 7010500 AT etr-usa DOT com> <00ad01cd7bf6$7cc68a50$76539ef0$@motionview3d.com> <1345169297 DOT 10004 DOT 10 DOT camel AT YAAKOV04> <87k3qmedzh DOT fsf AT Rainer DOT invalid> <51194F7F DOT 8050403 AT etr-usa DOT com> <87halio886 DOT fsf AT Rainer DOT invalid> <511967DD DOT 8030600 AT etr-usa DOT com> <87d2w6o6iq DOT fsf AT Rainer DOT invalid> <5119E08B DOT 6050909 AT etr-usa DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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: 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 Hi Warren, Warren Young etr-usa.com> writes: > 4. Profit! Still not sure about that... If I check out the 3.7.15.2 version and just configure / make, I'll get a seemingly working sqlite3.exe, but I can't compile the testfixture. How do you configure the build on Cygwin and how'd you work around the reams of errors in compiling the testfixture (if you had to do anything)? When weeding out the "Cygwin is Windows" stuff from configure.ac, I'll get past that hurdle and a fairly clean compile of everything (I haven't checked the whole output, so it may actually be completely clean). There are a few test errors that are probably harmless, but the testsuite does indeed produce a few of the dreaded disk I/O errors that seem to have serious consequences. At least during the "big file" test I found that while the sqlite from Cygwin _does_ place a lock on that file, it isn't exclusive -- so you can open the file from a Windows application again or rename it. So it seems that indeed the locking stuff is what keeps this from working correctly. Not sure when I'll find some time to dive into the sources, but if anybody has some ideas, keep 'em coming. Regards, Achim. -- 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