^ cryptolib.c: At top level: cryptolib.c:359:8: error: unknown type name ‘CRYPTO_ONCE’ static CRYPTO_ONCE once_read = CRYPTO_ONCE_STATIC_INIT; ^ === This is an issue at stable === ------------------------------------------------------------------- This is an stable amd64 chroot image at a tinderbox (==build bot) name: 13.0-systemd_stable-libressl_20171021-112841 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * llvm-config: 3.9.1 Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: emerge -qpv dev-lang/swi-prolog [ebuild N ] dev-lang/swi-prolog-7.4.2 USE="berkdb gmp hardened libedit libressl readline ssl zlib -X -archive -debug -doc -java -minimal -odbc -static-libs {-test} -uuid"
Created attachment 499764 [details] emerge-info.txt
Created attachment 499766 [details] dev-lang:swi-prolog-7.4.2:20171023-070524.log
Created attachment 499768 [details] emerge-history.txt
Created attachment 499770 [details] environment
Created attachment 499772 [details] etc.portage.tbz2
Created attachment 499774 [details] logs.tbz2
This particular bug has been fixed upstream for some time now. Thanks for reporting this.