Summary: | dev-libs/libgit2-glib-0.24.4[libressl] : /.../libgit2.so: undefined reference to `BIO_meth_set_gets' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | mgorny, steils |
Priority: | Normal | Keywords: | Inclusion, PATCH |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://github.com/libgit2/libgit2/pull/4043 | ||
See Also: | https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219362 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 561854 | ||
Attachments: |
emerge-info.txt
config.log dev-libs:libgit2-glib-0.24.4:20170124-063906.log emerge-history.txt environment etc.portage.tbz2 |
Description
Toralf Förster
2017-01-24 09:59:15 UTC
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 |