Mark Phippard <markp...@gmail.com> writes:
> On Mon, Oct 10, 2011 at 4:19 PM, Philip Martin
> <philip.mar...@wandisco.com> wrote:
>> Barry Scott <ba...@barrys-emacs.org> writes:
>>
>>> I'm trying to build subversion 1.7.0-rc4 on Mac OS X 10.7.
>>> And I'm guessing that got something in the build/install wrong.
>>>
>>> I see the following error from svn checkout:
>>>
>>> $ /usr/local/svn-1.7.0-rc4/bin/svn checkout
>>> file:///Users/barry/BuildTemp/Darwin_body/svn-1.7.0-rc4/py27_pysvn_apple_com/Tests/testroot-01/repos/trunk
>>>
>>> /Users/barry/BuildTemp/Darwin_body/svn-1.7.0-rc4/py27_pysvn_apple_com/Tests/testroot-01/wc1
>>> svn: E200029: Couldn't perform atomic initialization
>>> svn: E200030: Could not initialize SQLite shared cache
>>>
>>> Does anyone know what can cause this, or point me to the area of code
>>> to check?
>>
>> libsvn_subr/sqlite.c:init_sqlite()
>>
>> /* SQLite 3.5 allows sharing cache instances, even in a multithreaded
>> environment. This allows sharing cached data when we open a database
>> more than once (Very common in the current pre-single-database state) */
>> SQLITE_ERR_MSG(sqlite3_enable_shared_cache(TRUE),
>> _("Could not initialize SQLite shared cache"));
>>
>>
>> Which version of SQLite are you using?
>
> This is the version that comes with OSX 10.7:
>
> $ /usr/bin/sqlite3 -version
> 3.7.5
Looking at sqlite.h I see this comment on sqlite3_enable_shared_cache:
** ^Note: This method is deprecated on MacOS X 10.7 and iOS version 5.0
** and will always return SQLITE_MISUSE, instead of calling this function
** shared cache mode should be enabled per-database connection via
** sqlite3_open_v2 with SQLITE_OPEN_SHAREDCACHE instead.
--
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com
