In file included from /var/tmp/portage/dev-libs/libgit2-0.26.8/work/libgit2-0.26.8/src/global.c:14: /var/tmp/portage/dev-libs/libgit2-0.26.8/work/libgit2-0.26.8/src/openssl_stream.h:32:25: error: static declaration of ‘BIO_meth_new’ follows non-static declaration GIT_INLINE(BIO_METHOD*) BIO_meth_new(int type, const char *name) ^~~~~~~~~~~~ In file included from /usr/include/openssl/evp.h:67, ------------------------------------------------------------------- This is an stable amd64 chroot image at a tinderbox (==build bot) name: 17.0-hardened_stable-libressl_20190503-095707 ------------------------------------------------------------------- Please see the tracker bug for details. gcc-config -l: [1] x86_64-pc-linux-gnu-8.2.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) * emerge -qpvO dev-libs/libgit2 [ebuild N ] dev-libs/libgit2-0.26.8 USE="curl libressl ssh threads -examples -gssapi -test -trace"
Created attachment 575070 [details] emerge-info.txt
Created attachment 575072 [details] dev-libs:libgit2-0.26.8:20190504-034401.log
Created attachment 575074 [details] emerge-history.txt
Created attachment 575076 [details] environment
Created attachment 575078 [details] etc.portage.tbz2
Created attachment 575080 [details] logs.tbz2
Created attachment 575082 [details] temp.tbz2
Does not reproduce with libgit2-0.28.1.
(In reply to Stefan Strogin from comment #8) > Does not reproduce with libgit2-0.28.1. Did you test with libressl?
(In reply to Michał Górny from comment #9) > (In reply to Stefan Strogin from comment #8) > > Does not reproduce with libgit2-0.28.1. > > Did you test with libressl? can't speak for steils, but 3 LibreSSL tinderbox images emerged it here ;)