Jay, Thanks for your reply.
>It might make more sense to install a newer version in /usr/local > rather than /usr. That way you can use the updated version for your That is what I did. I downloaded and extracted the .bin file and copied it to /usr/local/bin. Then after chmod +x it I ran it and got the Bus error. By what you are saying it appears that the one I already had in /usr/local/bin was not the original OS X version, so maybe it was installed by another application. I do have an older version in /usr/bin which is ostensibly the OS X delivered version. Any other suggestions? Thanks, Mark Jay A. Kreibich wrote: > On Sat, Jan 03, 2009 at 02:44:59PM -0500, Mark Fraser scratched on the wall: > >> I am trying to update the version 3.4.0 that came with my Mac OSX x86 >> Tiger installation. >> >> Any suggestions on the best way to do this? >> > > Mac OS X, by default, dynamically links just about everything, so it > is no surprise that Apple has chosen to build SQLite this way as well. > Apple's version of sqlite3 (/usr/bin/sqlite3) really is just the CLI > code, and doesn't contain the core SQLite engine. If you want to > upgrade the whole thing you need to upgrade both the CLI application > at /usr/bin/sqlite3 and the library at /usr/lib/libsqlite3.0.dylib. > > > > I'd be very cautious about doing that, however, as Apple uses SQLite > for many thing, including the Core Data framework. It is considered > part of the core OS. That also means System Updates may over-write > your changes. > > It might make more sense to install a newer version in /usr/local > rather than /usr. That way you can use the updated version for your > own projects and applications, but leave the OS version alone. That > also protects against Apple "updating" your installed version. > > -j > > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
