g-ir-scanner: link: /bin/sh ../libtool --mode=link --tag=CC x86_64-pc-linux-gnu-gcc -o /var/tmp/portage/dev-libs/libgit2-glib-0.24.4/work/libgit2-glib-0.24.4/libgit2-glib/tmp-introspect9NBLXA/Ggit-1.0 -export-dynamic -O2 -pipe -march=native -Wall -Wl,-O1 -Wl,--as-needed tmp-introspect9NBLXA/var/tmp/portage/dev-libs/libgit2-glib-0.24.4/work/libgit2-glib-0.24.4/libgit2-glib/tmp-introspect9NBLXA/Ggit-1.0.o -L. libgit2-glib-1.0.la -Wl,--export-dynamic -lgmodule-2.0 -pthread -lgit2 -lgio-2.0 -lgobject-2.0 -lglib-2.0 libtool: link: x86_64-pc-linux-gnu-gcc -o /var/tmp/portage/dev-libs/libgit2-glib-0.24.4/work/libgit2-glib-0.24.4/libgit2-glib/tmp-introspect9NBLXA/.libs/Ggit-1.0 -O2 -pipe -march=native -Wall -Wl,-O1 tmp-introspect9NBLXA/var/tmp/portage/dev-libs/libgit2-glib-0.24.4/work/libgit2-glib-0.24.4/libgit2-glib/tmp-introspect9NBLXA/Ggit-1.0.o -Wl,--export-dynamic -pthread -Wl,--export-dynamic -Wl,--as-needed -L. ./.libs/libgit2-glib-1.0.so -lgmodule-2.0 -lgit2 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -pthread /usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/../../../../lib64/libgit2.so: undefined reference to `BIO_meth_set_gets' ----------------------------------------------------------------- This is an unstable amd64 chroot image (named 13.0-no-multilib-libressl-unstable_20170122-225602) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * llvm-config --version: 3.9.1 Available Python interpreters, in order of preference: [1] python3.4 [2] python3.5 (fallback) [3] python2.7 (fallback) java-config: -----------------------------------------------------------------
Created attachment 461168 [details] emerge-info.txt
Created attachment 461170 [details] config.log
Created attachment 461172 [details] dev-libs:libgit2-glib-0.24.4:20170124-063906.log
Created attachment 461174 [details] emerge-history.txt
Created attachment 461176 [details] environment
Created attachment 461178 [details] etc.portage.tbz2
I read from libgit2 changelog that it is now (since 0.26.0) compatible with OpenSSL v1.1, maybe that was the problem here?
Could be the libressl USE flag ? libgit2 ships with src/openssl_stream.{c,h} that checks for openssl < 1.1 to define these symbols, maybe libressl messes with that ?
Some more search show this is the actual problem.
Does not reproduce with dev-libs/libgit2-0.28.1 and libressl-2.8.3 Appears it was fixed upstream here: https://github.com/libgit2/libgit2/commit/d9007dc8520942763a21e4058dfa8f159f3e3c56