This is the mail archive of the
mailing list for the Cygwin project.
Re: [bug] Something fishy going on with sqlite3...
- From: Warren Young <warren at etr-usa dot com>
- To: Cygwin-L <cygwin at cygwin dot com>
- Date: Tue, 03 Apr 2012 17:58:18 -0600
- Subject: Re: [bug] Something fishy going on with sqlite3...
- References: <87aa3hd4a5.fsf@Rainer.invalid> <firstname.lastname@example.org> <8762e5d3le.fsf@Rainer.invalid> <email@example.com> <871uotd0ub.fsf@Rainer.invalid> <firstname.lastname@example.org> <loom.20120316T080148email@example.com> <loom.20120403T153444firstname.lastname@example.org>
On 4/3/2012 8:05 AM, Achim Gratz wrote:
The solution to this riddle: sqlite3 wrongly infers Cygwin as SQLITE_OS_WIN.
Forcing a define for SQLITE_OS_UNIX produces an executable that works with temp
store to disk even when the user is not an administrator.
Additionally, the good folks at SQLite.org changed their naming scheme, so I've
had to come up with a new cygport definition.
Send me the cygport file and I'll build new sqlite3 packages.
(If you're wondering why I haven't responded to this thread before now,
it's because this is the first post to the thread that told me there was
a problem with the package.)
Cygwin sqlite3 package maintainer
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple