Warren Young etr-usa.com> writes:
>
> Will you please try them?
>
Looks good to me, but hasn't seen extensive testing.
> There is likely to be one difference w.r.t your version, which is that
> my packages include a patch to replace a deprecated Cygwin 1.5
> cygwin1.dll call with its modern
Warren Young writes:
> I've rebuilt the packages and uploaded them here:
>
> wget \
> http://etr-usa.com/cygwin/sqlite3/sqlite3-3.07.11.00-1.tar.bz2 \
> http://etr-usa.com/cygwin/sqlite3/sqlite3-3.07.11.00-1-src.tar.bz2 \
> http://etr-usa.com/cygwin/sqlite3/libsqlite3_0-3.07.11.00-1.tar.bz2 \
>
On 4/4/2012 5:07 AM, Achim Gratz wrote:
Warren Young etr-usa.com> writes:
Send me the cygport file and I'll build new sqlite3 packages.
---8<->8---
ORIG_PN="sqlite"
ORIG_PV=`echo $PV|tr . \ |\
awk -e '{printf "%1d%02d%02d%02d",$1,$2,$3,$4;}'`
Thanks for taking the time to diagnose thi
Warren Young etr-usa.com> writes:
>
> Send me the cygport file and I'll build new sqlite3 packages.
I've just made a local patch package, tests look good so far.
Specifically, I can now build the Perl DBD::SQLite module (either with
the bundled SQLite or the locally installed library) and have a
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.o
Achim Gratz NexGo.DE> writes:
>
> I'm stumped...
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
René Berber computer.org> writes:
> How do you set them to go into files?
In my initial tests? Not at all, that was the default (I may be able to
override that in the system or user configuration, but have not touched anything
there). When I compile SQLite with SQLITE_TEMP_STORE=3 (memory only)
On 3/15/2012 3:13 PM, Achim Gratz wrote:
>> sqlite> .schema two
>> CREATE TABLE two (
>> id INTEGER NOT NULL,
>> name CHAR (64) NOT NULL
>> );
>>
>> No access denied. The file test is created in the same directory, also
>> .sqlite_history .
>
> In case it wasn't clear in my first posting, I can
René Berber writes:
> Right. Problem is I can't reproduce the error.
I don't have any better information at the moment.
> I'm not using a snapshot, I'm at "1.7.11(0.260/5/3) 2012-02-24", and the
> operation you show, using mintty:
I've switched to snapshots due to other problems (no Ctrl-C in
On 3/15/2012 2:14 PM, Achim Gratz wrote:
> René Berber writes:
>> The obvious question: what is your $TMP ?
>
> Obvious maybe — but TMP doesn't get invoked. :-)
>
> SQLite tries to create the file in the current working directory.
> Again, if I do that from a windows console window, all is wel
René Berber writes:
> The obvious question: what is your $TMP ?
Obvious maybe — but TMP doesn't get invoked. :-)
SQLite tries to create the file in the current working directory.
Again, if I do that from a windows console window, all is well, if I do
it from mintty I get an access denied error.
On 3/15/2012 1:59 PM, Achim Gratz wrote:
>
> I've been trying to troubleshoot an SQLite failure that boils down to
> this: SQLite catches an access denied error when trying to create a
> _temporary_ table and only when sqlite3 is run from mintty. If I do the
> same thing in a console, all is well
I've been trying to troubleshoot an SQLite failure that boils down to
this: SQLite catches an access denied error when trying to create a
_temporary_ table and only when sqlite3 is run from mintty. If I do the
same thing in a console, all is well (as I found out when trying to
strace the sqlite3
13 matches
Mail list logo
