apsw compiling error(AttributeError: 'module' object has no attribute 't1_dump')

[dassio]

i try to install S3QL on fedora , but i think i have some problem with fedora sqlite3 when compiling apsw.
here is what i did :

-----run python setup.py install

running install
running build
running build_ext
SQLite: Using system sqlite include/libraries
running install_lib
running install_egg_info
Removing /usr/lib/python2.7/site-packages/apsw-3.7.13_r1-py2.7.egg-info
Writing /usr/lib/python2.7/site-packages/apsw-3.7.13_r1-py2.7.egg-info
-------run locate apsw.so
/home/danny/amazons3/apsw-3.7.13-r1/build/lib.linux-i686-2.7/apsw.so
/usr/lib/python2.7/site-packages/apsw.so
--------run lld /usr/lib/python2.7/site-packages/apsw.so
    linux-gate.so.1 =>  (0xb7757000)
    libpython2.7.so.1.0 => /lib/libpython2.7.so.1.0 (0xb74e2000)
    libpthread.so.0 => /lib/libpthread.so.0 (0xb74c8000)
    libc.so.6 => /lib/libc.so.6 (0xb731a000)
    libdl.so.2 => /lib/libdl.so.2 (0xb7315000)
    libutil.so.1 => /lib/libutil.so.1 (0xb7310000)
    libm.so.6 => /lib/libm.so.6 (0xb72e5000)
    /lib/ld-linux.so.2 (0x4fc8a000)

[dassio]

here is more info about my sqlite3 installation and i am on fedora17:
-----run locate sqlite3.so
/usr/lib/libsqlite3.so
/usr/lib/libsqlite3.so.0
/usr/lib/libsqlite3.so.0.8.6
/usr/lib/php/modules/sqlite3.so
/usr/lib/php-zts/modules/sqlite3.so
/usr/lib/python2.7/lib-dynload/_sqlite3.so
/usr/lib/xulrunner-2/libmozsqlite3.so
/usr/local/lib/libsqlite3.so
/usr/local/lib/libsqlite3.so.0
/usr/local/lib/libsqlite3.so.0.8.6

[dassio]

the question is now i think how can i make apsw dynamically linked to sqlite3?  i tried to remove the fetch parameter, but it doesn't help, anyone has any ideas ?

[Nikolaus Rath]

On 07/26/2012 01:46 AM, dassio wrote:
> i try to install S3QL on fedora , but i think i have some problem with
> fedora sqlite3 when compiling apsw.
> here is what i did :
>

> -----run* python setup**.py install*
>
> /running install

> running build
> running build_ext
> SQLite: Using system sqlite include/libraries
> running install_lib
> running install_egg_info
> Removing /usr/lib/python2.7/site-packages/apsw-3.7.13_r1-py2.7.egg-info

> Writing /usr/lib/python2.7/site-packages/apsw-3.7.13_r1-py2.7.egg-info/
> -------run *locate apsw.so*

locate will not be up-to-date without a prior call to updatedb.

> //home/danny/amazons3/apsw-3.7.13-r1/build/lib.linux-i686-2.7/apsw.so
> /usr/lib/python2.7/site-packages/apsw.so/
> --------run *lld //usr/lib/python2.7/site-packages/apsw.so/*

Are you sure this is the file that was installed by setup.py?


Best,

-Nikolaus

--
�Time flies like an arrow, fruit flies like a Banana.�

PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C

[dassio]

no, i am not sure now. i tried on another computer and it doesn't work the same anymore, i think the apsw.so is created with the fetch paramter.

anyway now  i tried compiling and installing sqlite-3.7.13, i still got the error:Your SQLite version is too old. It must be at least 3.7.13. even when i removed the OS's sqlite.

this is the result when i installed sqlite from source and remove the OS's sqlite:

[root@dassio-find apsw-3.7.13-r1]# updatedb;locate sqlite3.so

    /root/sqlite-autoconf-3071300/.libs/libsqlite3.so

    /root/sqlite-autoconf-3071300/.libs/libsqlite3.so.0

    /root/sqlite-autoconf-3071300/.libs/libsqlite3.so.0.8.6

[root@dassio-find apsw-3.7.13-r1]# python setup.py install

running install

running build

running build_ext

SQLite: Using system sqlite include/libraries

building 'apsw' extension

gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -DEXPERIMENTAL=1 -DNDEBUG=1 -DAPSW_FORK_CHECKER=1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -Isrc -I/usr/include/python2.7 -c src/apsw.c -o build/temp.linux-x86_64-2.7/src/apsw.o

src/apsw.c:62:2: error: #error Your SQLite version is too old. It must be at least 3.7.13

In file included from /usr/include/python2.7/pyconfig.h:6:0,

                 from /usr/include/python2.7/Python.h:8,

                 from src/apsw.c:73:

/usr/include/python2.7/pyconfig-64.h:1170:0: warning: "_POSIX_C_SOURCE" redefined [enabled by default]

In file included from /usr/include/assert.h:37:0,

                 from src/apsw.c:66:

/usr/include/features.h:164:0: note: this is the location of the previous definition

In file included from /usr/include/python2.7/pyconfig.h:6:0,

                 from /usr/include/python2.7/Python.h:8,

                 from src/apsw.c:73:

/usr/include/python2.7/pyconfig-64.h:1192:0: warning: "_XOPEN_SOURCE" redefined [enabled by default]

In file included from /usr/include/assert.h:37:0,

                 from src/apsw.c:66:

/usr/include/features.h:166:0: note: this is the location of the previous definition

In file included from src/apsw.c:140:0:

src/connection.c: In function ‘Connection_db_filename’:

src/connection.c:3227:6: warning: assignment discards ‘const’ qualifier from pointer target type [enabled by default]

src/apsw.c: In function ‘initapsw’:

src/apsw.c:1648:7: error: ‘SQLITE_CANTOPEN_ISDIR’ undeclared (first use in this function)

src/apsw.c:1648:7: note: each undeclared identifier is reported only once for each function it appears in

src/apsw.c:1703:7: error: ‘SQLITE_OPEN_MEMORY’ undeclared (first use in this function)

src/apsw.c:1773:7: error: ‘SQLITE_DBSTATUS_CACHE_WRITE’ undeclared (first use in this function)

error: command 'gcc' failed with exit status 1

On Thursday, July 26, 2012 9:07:41 PM UTC+8, Nikolaus Rath wrote:

On 07/26/2012 01:46 AM, dassio wrote:
> i try to install S3QL on fedora , but i think i have some problem with
> fedora sqlite3 when compiling apsw.
> here is what i did :
>
> -----run* python setup**.py install*
>
> /running install
> running build
> running build_ext
> SQLite: Using system sqlite include/libraries
> running install_lib
> running install_egg_info
> Removing /usr/lib/python2.7/site-packages/apsw-3.7.13_r1-py2.7.egg-info
> Writing /usr/lib/python2.7/site-packages/apsw-3.7.13_r1-py2.7.egg-info/
> -------run *locate apsw.so*

locate will not be up-to-date without a prior call to updatedb.

> //home/danny/amazons3/apsw-3.7.13-r1/build/lib.linux-i686-2.7/apsw.so
> /usr/lib/python2.7/site-packages/apsw.so/
> --------run *lld //usr/lib/python2.7/site-packages/apsw.so/*

Are you sure this is the file that was installed by setup.py?


Best,

   -Nikolaus

--

 ï¿½Time flies like an arrow, fruit flies like a Banana.�

[dassio]

sorry i forget to install the sqlite, now i am at the same situation like here: https://groups.google.com/forum/?fromgroups#!topic/s3ql/vvgo6a3Fa_Q 

[Nikolaus Rath]

On 07/26/2012 10:42 AM, dassio wrote:
> no, i am not sure now. i tried on another computer and it doesn't work

> the same anymore, i think the *apsw.s*o is created with the *fetch*

> paramter.
> anyway now i tried compiling and installing sqlite-3.7.13, i still got

> the error:*Your SQLite version is too old. It must be at least 3.7.13.
> *even when i removed the OS's sqlite.

If you are able to compile apsw with *fetch*, but getting a "version too
old' error without it, then you have either not correctly installed
sqlite, or there are still remains of the Fedora SQLite package left
that you need to remove.

[Nikolaus Rath]

On 07/26/2012 12:24 PM, dassio wrote:
> sorry i forget to install the sqlite, now i am at the same situation
> like here:
> https://groups.google.com/forum/?fromgroups#!topic/s3ql/vvgo6a3Fa_Q

> <https://groups.google.com/forum/?fromgroups#%21topic/s3ql/vvgo6a3Fa_Q>

So, what happens if you follow the advice in that thread? Does
increasing the timeout fix the test?

[dassio]

i think it works now here is the result:
test_passphrase (tests.t4_adm.AdmTests) ... Warning: maximum object sizes less than 1 MB will seriously degrade performance.
ok
runTest (tests.t4_fuse.fuse_tests) ... Warning: maximum object sizes less than 1 MB will seriously degrade performance.
ok
runTest (tests.t5_cp.cpTests) ... Warning: maximum object sizes less than 1 MB will seriously degrade performance.
ok
runTest (tests.t5_ctrl.CtrlTests) ... Warning: maximum object sizes less than 1 MB will seriously degrade performance.
ok
runTest (tests.t5_fsck.FsckTests) ... Warning: maximum object sizes less than 1 MB will seriously degrade performance.
ok
runTest (tests.t5_full.FullTests) ... Warning: maximum object sizes less than 1 MB will seriously degrade performance.
ok
runTest (tests.t5_lock_rm.LockRemoveTests) ... Warning: maximum object sizes less than 1 MB will seriously degrade performance.
ok
Ran 160 tests in 155.589s
OK (skipped=32)