Re: [APSW 3.3.13-r1] Fails compiling in CentOS?

Fred <[email protected]>
Newsgroups gmane.comp.python.db.pysqlite.user
Message-ID <[email protected]>
At 12:55 26/01/2008 -0800, Fred wrote:
>I guess either it takes more than just copying a .so file from one host to 
>the other, or maybe that there other dependencies like Glibc, GCC, etc.?

Looks like it could be due to compiling for a different instruction set: 
The CentOS host is i686, the AstLinux host is a i586:

=========
creating build/temp.linux-i686-2.4
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall 
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector 
--param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic 
-fasynchronous-unwind-tables -D_GNU_SOURCE -fPIC -fPIC -DNDEBUG=1 
-DEXPERIMENTAL=1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -Isqlite3 
-I/usr/include/python2.4 -c apsw.c -o build/temp.linux-i686-2.4/apsw.o
In file included from apsw.c:66:
statementcache.c: In function ‘statementcache_free’:
statementcache.c:99: warning: unused variable ‘res’
creating build/lib.linux-i686-2.4
gcc -pthread -shared build/temp.linux-i686-2.4/apsw.o -Lsqlite3 -lsqlite3 
-o build/lib.linux-i686-2.4/apsw.so
=========

Is it possible to tell the python build script to compile for i586?

Thank you.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.