<[EMAIL PROTECTED]> wrote on 01/30/2007 02:42:11 PM:

> [EMAIL PROTECTED] wrote:
> > Hello all,
> >
> > Question in a nutshell:   My compiler can't handle "typedef long long "
> > (sqlite3.h) --- Is there a workaround?
> >
> > There was an include file in /usr/include/sys, which is called xlong.h.
> > Inside there is a long note about how it addresses 64 bit expressions.
I am
> > not sure it is the correct thing to try,  but I #included it,  and
changed
> > the line 88 to say
> > typedef  xlong_t sqlite_int64 ;
> > and line 89 to say:
> > typedef unsigned xlong_t  sqlite_uint64;
> >
> > Almost worked......  Instead of complaining at the very first file it
tried
> > to compile,  it compiled about 15 source files, and then I get:
> > "./src/vdbemem.c", line 256: error: invalid cast expression
>
> Line 256 attempts to cast a double to type "i64".  "i64" is defined
> in sqliteInt.h:
>
>     typedef sqlite3_int64 i64;
>
> So apparently your compiler cannot cast a double to type xlong_t.
>
> Try setting sqlite3_int64 to just "int" and compiling with
> -DSQLITE_32BIT_ROWID=1.  That might work.
> --
> D. Richard Hipp  <[EMAIL PROTECTED]>
>
>
>
-----------------------------------------------------------------------------

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

>
    "So apparently your compiler cannot cast a double to type xlong_t."
That's because I did the earlier xlong stuff by hand.  I can try your above
recommendation, and let you know.

I should mention 1: That I am running SCO Openserver 5 [popularity not
withstanding], and 2: That I had to change the makefile because the vanilla
make on my system does not like "TCC +=" style entries.

I probably should ask my question this way: What is the *safe* method for
32 bit machines to build Sqlite 3.3x?

Thank you very much for such a fast reply!


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

Reply via email to