I tried to build sqlite 3.4.2 on Solaris 8, 64 bits.
My existing gcc setup failed to do it, but I could do it with the Sun compiler 5.3.

I configured with:
../sqlite-3.4.2/configure --enable-debug --enable-threadsafe --with-tcl=/usr/local/lib/sparcv9 CFLAGS='-DSQLITE_MEMDEBUG=2 -DSQLITE_TEST=1 -DSQLITE_DEBUG=1 -DSUN_CC=1' CC='cc -xarch=v9'

Building encountered 3 problems:

1. tool/lemon.c line 111 redefines B_FALSE and B_TRUE; this conflicts with a similar definition in (one of the) types.h; you may try to define POSIX_C_SOURCE or else XOPEN_SOURCE, but that breaks struct timeval later in the build; it seems the configure should test for the existence of boolean_t or bool_t and if it exists should typedef Boolean to boolean_t; else it should keep the current enum line
In the above configure line SUN_CC is my simple way to do that

2. testfixture needs -lrt (for sched_yield) - had to edit the Makefile

3. the linker /usr/ccs/bin/ld does neither understand nor need -64 - had to edit the LD definition in the libtool

Then I ran the fulltest and one test failed as follows:

printf-8.2...
Expected: [2147483647 2147483648 4294967295] ..... (which is 7FFFFFFF 80000000 FFFFFFFF) Got: [2147483647 18446744071562067968 18446744073709551615] ..... (which is 7FFFFFFF FFFFFFFF80000000 FFFFFFFFFFFFFFFF)


The tcl is 8.4.15 built with the same compiler

Does sqlite assume that a long is the same size as an int? Reading the test seems to point that way, but I think I better ask.
Do I have to find the compiler flag for that and build that way?
please advise, and thank  you very much,
yours truly,
Victor Secarin


---------------------------------------------------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient. Any review, 
use, distribution, or disclosure by others is strictly prohibited. If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.



-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to