Source: postfix
Version: 3.0.4-1
Severity: normal
Dear Maintainer,
What is the proper way of including LMDB support in Postfix 3.x? The rules seem
to have changed in the new series. Postfix 2.11 has been previously built
successful in the same environment:
[ debian/rules for 3.x]:
CCARGS += -DDEBIAN -DHAS_PCRE -DHAS_LDAP -DUSE_LDAP_SASL \
-DHAS_SQLITE -DMYORIGIN_FROM_FILE \
$(shell getconf LFS_CFLAGS) \
-DHAS_CDB \
-DHAS_LMDB -I/usr/include \
-DHAS_MYSQL -I/usr/include/mysql \
-DHAS_PGSQL -I`pg_config --includedir` \
-DHAS_SQLITE -I/usr/include \
-DHAS_SSL -I/usr/include/openssl \
-DUSE_SASL_AUTH -I/usr/include/sasl \
-DUSE_CYRUS_SASL \
-DUSE_TLS
AUXLIBS += -lssl -lcrypto -lsasl2 -lpthread
AUXLIBS_LMDB="-L/usr/lib -llmdb -lpthread"
Above recipe fails to include LMDB support using "dpkg-buildpackage".
Compiled postconf output:
$ postconf -m
btree
cdb
cidr
environ
fail
hash
inline
internal
memcache
nis
pcre
pipemap
proxy
randmap
regexp
socketmap
sqlite
static
tcp
texthash
unionmap
unix
-- System Information:
Debian Release: 8.3
APT prefers stable
APT policy: (1001, 'stable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
