x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -O2 -pipe -march=native -Wall -c -o ssli_openssl.o ssli_openssl.c ssli_openssl.c: In function ‘SSLi_init’: ssli_openssl.c:237:2: error: unknown type name ‘EC_KEY’ EC_KEY *ecdhkey = EC_KEY_new_by_curve_name(NID_X9_62_prime256v1); ^~~~~~ ssli_openssl.c:237:20: warning: implicit declaration of function ‘EC_KEY_new_by_curve_name’ [-Wimplicit-function-declaration] ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-gnome-systemd_20170815-183537 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) * [2] ruby22 (with Rubygems) java-config: The following VMs are available for generation-2: emerge -qpv media-sound/umurmur [ebuild N ] media-sound/umurmur-0.2.17-r1 USE="-gnutls -libressl -shm"
Created attachment 489608 [details] emerge-info.txt
Created attachment 489610 [details] emerge-history.txt
Created attachment 489612 [details] environment
Created attachment 489614 [details] etc.portage.tbz2
Created attachment 489616 [details] logs.tbz2
Created attachment 489618 [details] media-sound:umurmur-0.2.17-r1:20170819-055416.log
Created attachment 489620 [details] temp.tbz2
isn't this a libressl thing
(In reply to Alex Xu (Hello71) from comment #8) Neither the image name (#comment 0) nor the emerge history show that IMO.
Might be USE=bindist.
Fixed in 0.2.18+ (https://github.com/umurmur/umurmur/commit/4a8373bd0aa4711f4d1a4eaffcf00ca6e555b3ab) and probably bindist anyway.
