[sqlite] unresolved external '__faststorefence' referenced from sqlite3.o

On 23-11-15 15:23, Richard Hipp wrote: > On 11/23/15, Johan W. Van Ooijen wrote: >> On 23-11-15 15:01, Richard Hipp wrote: >> > Try compiling with -DSQLITE_MEMORY_BARRIER="" >> >> This will produce an empty sqlite3MemoryBarrier() function; is such

[sqlite] unresolved external '__faststorefence' referenced from sqlite3.o

On 23-11-15 15:01, Richard Hipp wrote: > Try compiling with -DSQLITE_MEMORY_BARRIER="" This will produce an empty sqlite3MemoryBarrier() function; is such a memory barrier not necessary under 32-bit and/or 64-bit Windows? Regards, Johan Van Ooijen

[sqlite] unresolved external '__faststorefence' referenced from sqlite3.o

In trying to find a solution to the unresolved external '__faststorefence' problem I get with the SQLite 3.9.2 amalgamation under Embarcadero C++Builder XE7, I see that macro SQLITE_OS_WIN is used on lines 9153 and 9169, whereas SQLITE_OS_WIN becomes #defined after line 11225. This does not see

[sqlite] unresolved external '__faststorefence' referenced from sqlite3.o

Hello, I am upgrading from SQLite 3.8.5 to 3.9.2, using the standard amalgamation source code (no changes, no conditional defines). The compiler I am using is Embarcadero C++Builder XE7, which uses a Clang-based (LLVM) 64-bit compiler. When building a 32-bit version of my MS-Windows-executable