libtool: compile: x86_64-pc-linux-gnu-gcc -O2 -pipe -march=native -DSQLITE_HAS_CODEC -DSQLCIPHER_CRYPTO_OPENSSL -DSQLITE_OS_UNIX=1 -I. -I/var/tmp/portage/dev-db/sqlcipher-3.4.2/work/sqlcipher-3.4.2/src -I/var/tmp/portage/dev-db/sqlcipher-3.4.2/work/sqlcipher-3.4.2/ext/rtree -I/var/tmp/portage/dev-db/sqlcipher-3.4.2/work/sqlcipher-3.4.2/ext/icu -I/var/tmp/portage/dev-db/sqlcipher-3.4.2/work/sqlcipher-3.4.2/ext/fts3 -I/var/tmp/portage/dev-db/sqlcipher-3.4.2/work/sqlcipher-3.4.2/ext/async -I/var/tmp/portage/dev-db/sqlcipher-3.4.2/work/sqlcipher-3.4.2/ext/session -D_HAVE_SQLITE_CONFIG_H -DBUILD_sqlite -DNDEBUG -DSQLITE_THREADSAFE=1 -DSQLITE_ENABLE_FTS3 -DSQLITE_ENABLE_FTS4 -DSQLITE_ENABLE_FTS5 -DSQLITE_ENABLE_JSON1 -DSQLITE_TEMP_STORE=2 -c sqlite3.c -fPIC -DPIC -o .libs/sqlite3.o sqlite3.c:21642:18: error: static declaration of ‘HMAC_CTX_new’ follows non-static declaration static HMAC_CTX *HMAC_CTX_new(void) ^~~~~~~~~~~~ In file included from sqlite3.c:21630:0: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib-hardened_libressl_20180506-210133 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby23 (with Rubygems) * emerge -qpv dev-db/sqlcipher [ebuild N ] dev-db/sqlcipher-3.4.2 USE="libressl readline -libedit -static-libs -tcl {-test}"
Created attachment 530716 [details] emerge-info.txt
Created attachment 530718 [details] dev-db:sqlcipher-3.4.2:20180510-120728.log
Created attachment 530720 [details] emerge-history.txt
Created attachment 530722 [details] environment
Created attachment 530724 [details] etc.portage.tbz2
Created attachment 530726 [details] logs.tbz2
Created attachment 530728 [details] temp.tbz2
Can not reproduce it on current stable and unstable Do you use hardmasked =libressl-2.7.*? It may be the culprit, upstream has some patches to be merged for it
This is supposed to be fixed upstream in >=dev-db/sqlcipher-4.0.0 (not in portage yet): https://github.com/sqlcipher/sqlcipher/issues/271
other bug has some patch links etc in it. *** This bug has been marked as a duplicate of bug 678502 ***