I haven't looked at whether this applies, but if the dbmail binary was
linked with the sqlite binary, via an *internal* libzdb object, then
it will fail to load at runtime without sqlite present. The database
driver object / shim driver which connects dbmail with the database
library needs to be runtime loaded in order to allow selection of
which backend to load based on what is configured and available.
Aaron
On May 19, 2008, at 2:24 AM, Paul J Stevens wrote:
You don't need to specify --with-mysql (or --with-postgresql or --
with-sqlite)
any more as of 2.3.3
With the inclusion of libzdb, dbmail will automatically support any
backend your
build of libzdb supports. Libzdb will (try to) detect automatically
what
backends are available on your system. Apparently you have the
development
libraries for sqlite3 available.
Not a problem.
Jorge Bastos wrote:
Hi Paul,
One question, using only:
Configure –with-mysql –with-sieve
This shouldn’t include SQLite into the binaries right?
I say this because:
---
ldd /usr/local/sbin/dbmail-lmtpd |grep -i lite
libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0xb7aa8000)
---
It should not be here, am I right?
Jorge
------------------------------------------------------------------------
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
