Thanks Armin! An upgrade from sqlite 3.3 to 3.6 solved this problem. Regards -David
2013/6/2 Armin Rigo <ar...@tunes.org> > Hi David, > > On Sun, Jun 2, 2013 at 1:51 AM, David Roid <datar...@gmail.com> wrote: > > CentOS 5.8 x64. The translation was successful with pypy-c generated, but > > subsequent packaging went wrong with following error: > > > > <snip> > > /root/pypy-2.0-src/lib_pypy/__pycache__/_cffi__gb0f282f4xe752c2be.c: > In > > function ‘_cffi_const_SQLITE_CREATE_VTABLE’: > > > /root/pypy-2.0-src/lib_pypy/__pycache__/_cffi__gb0f282f4xe752c2be.c:499: > > error: ‘SQLITE_CREATE_VTABLE’ undeclared (first use in this function) > > > /root/pypy-2.0-src/lib_pypy/__pycache__/_cffi__gb0f282f4xe752c2be.c:499: > > error: (Each undeclared identifier is reported only once > > > /root/pypy-2.0-src/lib_pypy/__pycache__/_cffi__gb0f282f4xe752c2be.c:499: > > error: for each function it appears in.) > > /root/pypy-2.0-src/lib_pypy/__pycache__/_cffi__gb0f282f4xe752c2be.c: > In > > function ‘_cffi_const_SQLITE_DROP_VTABLE’: > > > /root/pypy-2.0-src/lib_pypy/__pycache__/_cffi__gb0f282f4xe752c2be.c:577: > > error: ‘SQLITE_DROP_VTABLE’ undeclared (first use in this function) > > Look a bit above (in the <snip> part :-) what the first error message > produced by GCC is. It may likely be: cannot find #include > <sqlite3.h>. Either that or you have a broken or very out-of-date > version of sqlite3.h around. Either way I don't really understand, > given that you said it's not the case. For example in my old > sqlite3.h there is a line "#define SQLITE_DROP_VTABLE 30" which should > prevent the above error. > > > A bientôt, > > Armin. >
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
