On 2 Aug 2011, at 1:52pm, Viaduct Productions wrote: > 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.
Right. As long as they're all SQLite3 you're fine. (A little handwaving about some bugs you're very unlikely to trigger in old versions of SQLite.) > 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 That command-line is not a problem. It specifies compilation options but not any directories where files will end up. The only question is where you put your files. Just put your new files in new directories you make, not replace anything that already exists in /usr. If you're at all worried about this, do your development (including the compilation) using an account which isn't an administration account. Then it won't have the privileges to do anything bad. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
