Hi Simon Thanks for the reply. ya 3 it is. A package installed the 32 bit version, and now I have to install the 64 bit version, and I'm worried it might do irreparable things to my current tables. I'm thinking tables are independent of the binaries, so I'm good, but I wanted to check.
How do I leave the OS X entries alone? Ruby needs 64 bit SQLite, so I have to make sure it can see the new installation. This is what was recommended: CFLAGS='-arch i686 -arch x86_64' LDFLAGS='-arch i686 -arch x86_64' ./configure --disable-dependency-tracking Thanks again. Cheers _____________ Rich in Toronto On 2011-08-02, at 6:31 AM, Simon Slavin wrote: > As long as you stay with SQLite3, not SQLite2, The format of the files is > completely unchanged. You can create a database with one version, make > changes with another, then switch to a third one and query the data. > > By the way, in case you were considering this, do /not/ replace the SQLite > libraries/frameworks/headerfiles supplied with OS X. Don't mess with > /usr/bin or /usr/lib. That version is used by many System components and > changing it might make them malfunction. Make your own directory wherever > you want, put your 64-bit version in there, and use that for your own > programming and editing. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
