Interesting, thanks.
It is notorious that whoever maintains the RedHat package curiouly decided
a few years ago to break this and realese "a 0.8.6" version that does not
include sqlite3_prepare_v2() creating a lot of confusion. Can you confirm
that it is safe to nuke this crippled version and replace it with any
correct 0.8.6 ?
--A
On Sat, 25 Oct 2014 16:55:56 +0200, Dan Kennedy <danielk1...@gmail.com>
wrote:
On 10/25/2014 09:36 PM, Arnaud Meuret wrote:
Hi everyone,
On a fresh CentOS 5, compiling SQLite using the [current tarball][1]
for 3.8.7, the version being installed ends up in `/usr/local/lib` as
**3.8.6**:
bash-3.2# make install
make[1]: Entering directory `/mongrel2/sqlite-autoconf-3080700'
/bin/mkdir -p '/usr/local/lib'
/bin/sh ./libtool --mode=install /usr/bin/install -c
libsqlite3.la '/usr/local/lib'
libtool: install: /usr/bin/install -c .libs/libsqlite3.so.0.8.6
/usr/local/lib/libsqlite3.so.0.8.6
libtool: install: (cd /usr/local/lib && { ln -s -f
libsqlite3.so.0.8.6 libsqlite3.so.0 || { rm -f libsqlite3.so.0 && ln -s
libsqlite3.so.0.8.6 libsqlite3.so.0; }; })
libtool: install: (cd /usr/local/lib && { ln -s -f
libsqlite3.so.0.8.6 libsqlite3.so || { rm -f libsqlite3.so && ln -s
libsqlite3.so.0.8.6 libsqlite3.so; }; })
libtool: install: /usr/bin/install -c .libs/libsqlite3.lai
/usr/local/lib/libsqlite3.la
libtool: install: /usr/bin/install -c .libs/libsqlite3.a
/usr/local/lib/libsqlite3.a
[1]: https://www.sqlite.org/2014/sqlite-autoconf-3080700.tar.gz
Is it normal ? I expected to find libsqlite3.so.0.8.7.
It's normal. I think that number is only supposed to change if the new
release is not ABI compatible with the previous. It's a coincidence that
"8.6" matches the tail of the previous release number. Earlier releases
also used "libsqlite3.so.0.8.6".
Dan.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
