'$open_shared_object'/3: yaml4pl: cannot open shared object file: No such file or directory % PL-Unit: yaml ERROR: /var/tmp/portage/dev-lang/swi-prolog-7.7.11/work/swipl-7.7.11/packages/yaml/test_yaml.pl:80: test anchors: received error: setup_call_catcher_cleanup/4: Undefined procedure: yaml:yaml_parse_stream/2 ERROR: /var/tmp/portage/dev-lang/swi-prolog-7.7.11/work/swipl-7.7.11/packages/yaml/test_yaml.pl:81: test array: received error: setup_call_catcher_cleanup/4: Undefined procedure: yaml:yaml_parse_stream/2 ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-plasma-systemd_test_20180323-181400 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.7.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv dev-lang/swi-prolog [ebuild N ] dev-lang/swi-prolog-7.7.11 USE="X berkdb gmp libedit pcre readline ssl {test} zlib -archive -debug -doc -hardened -java -libressl -minimal -odbc -static-libs -uuid"
Created attachment 525554 [details] emerge-info.txt
Created attachment 525556 [details] dev-lang:swi-prolog-7.7.11:20180326-162343.log
Created attachment 525558 [details] emerge-history.txt
Created attachment 525560 [details] environment
Created attachment 525562 [details] etc.portage.tbz2
Created attachment 525564 [details] logs.tbz2
This is now fixed in swi-prolog-7.7.18-r1. Thanks for reporting this.