From 38fcd7062285f0400d436006c529a4211884bd8a Mon Sep 17 00:00:00 2001
From: rillig <rillig>
Date: Thu, 15 Nov 2007 14:11:53 +0000
Subject: The new thread-safe feature doesn't really work: The py-sqlite2
 self-test fails with a segmentation fault.

---
 databases/sqlite3/Makefile.common | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

(limited to 'databases')

diff --git a/databases/sqlite3/Makefile.common b/databases/sqlite3/Makefile.common
index b9b8738fb12..cc22695ea04 100644
--- a/databases/sqlite3/Makefile.common
+++ b/databases/sqlite3/Makefile.common
@@ -1,4 +1,4 @@
-# $NetBSD: Makefile.common,v 1.16 2007/11/15 10:39:18 rillig Exp $
+# $NetBSD: Makefile.common,v 1.17 2007/11/15 14:11:53 rillig Exp $
 
 DISTNAME=	sqlite-3.5.2
 PKGNAME=	${DISTNAME:S/-/3-/}
@@ -17,4 +17,11 @@ GNU_CONFIGURE=		yes
 USE_TOOLS+=		gmake
 USE_LIBTOOL=		yes
 
+# XXX: This option has been added for backwards compatibility after
+# updating to 3.5.2. Without it, py-sqlite2 crashes when trying to
+# access the mutex. The effect of this option is that multiple threads
+# may not use a _common_ database connection. They may access the
+# database through different database connections, though.
+CONFIGURE_ARGS+=	--disable-threadsafe
+
 PKGCONFIG_OVERRIDE=	sqlite3.pc.in
-- 
cgit v1.2.3