hi,
SQLite version 3.3.13 is now available in the usual place:
...
As always, please let me know if you find any problems.
building 3.3.13 on osx, all's seemingly well, except the process still
fails to build/install one file,
% cd /usr/ports/sqlite_build
% ls doc/whentouse.html
/
easy enough ...
@661
Makefile.in
install:sqlite3 libsqlite3.la sqlite3.h ${HAVE_TCL:1=tcl_install}
$(INSTALL) -d $(DESTDIR)$(libdir)
$(LTINSTALL) libsqlite3.la $(DESTDIR)$(libdir)
$(INSTALL) -d $(DESTDIR)$(exec_prefix)/bin
doing a clean build of v339 on osx 10.4.8.
% cd /projects/sqlite_build
% ../sqlite-3.3.9/configure --prefix=/usr/local/sqlite --enable-tcl
--enable-shared --enable-static --enable-debug --enable-threadsafe=yes
and,
% make
complete successfully.
at,
% make install
it fails at,
after building docs, on the "docs.html" page, there's a reference to
"whentouse.html",
Appropriate Uses For SQLite
when i click on it, it's a missing page.
looking in mybuild dir,
% ls doc/
arch.html datatype3.html oldnews.html
arch2.gif
comparing with apples' darwin-bundled sqlite src for an older sqlite
version (313 was it?), the addition of,
-DASSERT_VIA_CALLBACK=1 -DENABLE_LOCKING_CALLBACKS=1
as CFLAGS _seems_ to do the trick.
after applying the patch discussed earlier, then,
cd /projects/sqlite-3.3.8/configure
i've got an apparent RESOLUTION for some/most of the errors, & a
subsequent/new QUESTION ...
looking at the test code, the problem seems to be that,
::sqlite_opentemp_count 0
is never incremented from init val = 0.
that sure looks like temp file opening.
related, my current ./configur
whittling down the last few testsuite errors,
% ./testfixture ../sqlite-3.3.8/test/conflict.test
reports,
conflict-1.0... Ok
(...)
conflict-6.1... Ok
conflict-6.2...
Expected: [0 {7 6 9} 1 1]
Got: [0 {7 6 9} 1 0]
conflict-6.3...
> well, a 0.04% test failure rate ain't bad!
>
Are you, perchance, running this on a network filesystem of
some kind?
nope. all on my 'local' box.
just starting to look over these ...
i had NOT *defined* UTF8 as the encoding of choice ... or, at all,
actually. so, iirc, that means defaault t
FWIW, my MacBook has nothing special installed. The "About This Mac"
dialog box says "Mac OS X Version 10.4.8. 2GHz Intel Core Duo". I
searched through the Makefile that configure generated and there was
no sign of a -static flag anywhere. "gcc -v" says version 4.0.1,
(Apple Computer, Inc. bui
now, to check 'make fulltest', with,
% chown -R snowcrash /projects/b1
% chown -R snowcrash /projects/sqlite-3.3.8
% sudo -u snowcrash make fulltest
and see if this 'holds'.
with the mods i've made,
make fulltest
reports,
...
Thread-specific data deallocated properly
32 errors out of 80
this, apparently, is a real/known/old issue, at least @/by the 'fink'
proj (and, apparently, by ubuntu proj ...)
after working with the folks at IRC(#fink), and porting their 'old
version' patch,
# orig PATCH:
http://fink.cvs.sourceforge.net/fink/dists/10.4/unstable/main/finkinfo/database/sqlite
> can you tell me what, specifically, does 'just' this,
>
> cd b1
> ./testfixture ../sqlite/test/autovacuum_ioerr2.test
>
> report for you?
>
Thread-specific data deallocated properly
0 errors out of 1761 tests
well, for the life o' me, here, (now on 2 boxes @ home, and 2 @ work ...)
cd pr
On my system (which is generic as far as I know) this runs
to completion without any errors. (Actually, it is still
running as I type this, but no errors so far - certainly not
the cascade of errors you saw.)
I'm not sure what the difference is.
hrm. frustrating.
can you tell me what, specifi
just fyi,
i've now tested this on a different osx box, in order to try to rule
out something/anything 'environmental'. this box is, basically, a
'vanilla' osx install.
same problem -- same errors.
-
To unsubscribe, sen
checking readline header files... not specified: still searching...
checking readline.h usability... no
checking readline.h presence... no
checking for readline.h... no
checking for /usr/include/readline.h... configure: error: cannot check for file
existence when cross compiling
not sure on you
g'morning.
I think the -DSQLITE_TEST=1 option needs to be added only
when building testfixture, not when doing a regular build.
Doing this should clear up your randstr() problems.
joe w. also pointed this out. thanks.
but, as per my results in this thread/post,
http://article.gmane.org/gma
for completeness, here are the step-by-step details to reproduce the
error at hand,
cd /Users/snowcrash/projects
rm -rf sqlite-3.3.8*
wget http://www.sqlite.org/sqlite-3.3.8.tar.gz
gnutar zxvf sqlite-3.3.8.tar.gz
cd sqlite-3.3.8
unsetenv CFLAGS CPPFLAGS CXX CXXFLAGS LDFLAGS LDDLFLAGS LD_PREBIND
I'm not sure why you're compiling func.c seperately, or trying
to use a shared library for sqlite3 for testfixture - don't do this.
i'm not compiling func.c separately.
what i've reported here is an excerpt from the 'global' make.
i'm simply trying to narrow down the problem with 'simply' doin
sqlite/src/func.c
yes, i'm aware.
if i build v338 with,
#TCC += -DSQLITE_TEST=1
the build completes seemingly ok,
% sqlite3 -version
3.3.8
and the testsuite fails with the "randstr" error.
but, if i build with,
TCC += -DSQLITE_TEST=1
so that,
...
this is quite some merry chase ...
after a 'successful' build of v338 on osx, i see this test failure:
% ./testfixture ../test/autovacuum_ioerr2.test
autovacuum-ioerr2-1.1.1...
Error: no such function: randstr
autovacuum-ioerr2-1.1.2... Ok
autovacuum-ioerr2-1.1.3...
Expected: [1]
Got: [0]
au
make fulltest
seems to be happily grinding away on a seemingly huge test suite,
without a complaint ( so far ... ). i'll check back later ...
with the config as above, tests continue until,
...
server1-1.7... Ok
server1-1.8... Ok
server1-1.9... Ok
server1-1.10... Ok
server1-1.11... Ok
ser
this was very helpful.
with minor changes to your 'Makefile' for my env,
% cat Makefile
#!/usr/bin/make
TOP =/usr/ports/sqlite-3.3.8
AR = /usr/bin/ar -cr
RANLIB = /usr/bin/ranlib
NAWK = /usr/local/bin/gawk
BCC =
On my builds, all tests pass and collectively give about 98%
source code coverage. I never release unless all tests pass.
important to know, then. thanks.
I have spent entirely too much of
my life already trying to get my head around autoconf/libtool
and I do not intend to waste any more time
i'm building sqlite3.3.8 on osx.
the build, install & operation _seem_ to be ok,
.configure --prefix=/usr/local/sqlite --enable-threadsafe
--enable-cross-thread-connections --enable-threads-override-locks
--enable-tempstore=yes --enable-tcl --enable-debug
make
make instal
24 matches
Mail list logo
