On the contrary, the assert show above is a Very Good Thing. The ptr type is supposed to be a signed integer which is the same size as a pointer. The configure script is suppose to run some tests to pick the appropriate integer size and set a #define so that ptr can be defined appropriately. The assert() above verifies that all this happened correctly.
In your case, there is some kind of configuration problem and ptr is not being sized correctly. The assert above discovered this problem quickly so that you know the library is miscompiled, rather than letting the library run and generate subtle and hard-to-track errors.
You should be thankful for this assert. I has saved you a lot of debugging.
The configure script is suppose to set a macro named SQLITE_PTR_SZ to either 4 or 8. Like this:
-DSQLITE_PTR_SZ=8 -DSQLITE_PTR_SZ=4
What do you see when you compile? 4 or 8? Why is the configure script setting it incorrectly?
Thanks for help: looks like I've already fixed the problem by reusing SIZEOF_CHAR_P value detected on top-level configure script (available within KOffice build environment):
# define SQLITE_PTR_SZ SIZEOF_CHAR_P
I've asked Pentium 4 owners to check this out.
-- regards / pozdrawiam, Jaroslaw Staniek / OpenOffice Polska Developers wanted! Kexi Project: http://www.kexi-project.org KDElibs/Windows: http://wiki.kde.org/tiki-index.php?page=KDElibs+for+win32
