/var/tmp/portage/dev-libs/ell-0.5/work/ell-0.5/build-aux/test-driver: line 107: 7773 Aborted "$@" > $log_file 2>&1 FAIL: unit/test-uuid x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I/var/tmp/portage/dev-libs/ell-0.5/work/ell-0.5 -fvisibility=hidden -DUNITDIR=\""/var/tmp/portage/dev-libs/ell-0.5/work/ell-0.5/unit/"\" -DCERTDIR=\""./unit/"\" -O2 -pipe -march=native -fPIE -c -o unit/test-pbkdf2.o /var/tmp/portage/dev-libs/ell-0.5/work/ell-0.5/unit/test-pbkdf2.c /bin/sh ./libtool --tag=CC --mode=link x86_64-pc-linux-gnu-gcc -fvisibility=hidden -DUNITDIR=\""/var/tmp/portage/dev-libs/ell-0.5/work/ell-0.5/unit/"\" -DCERTDIR=\""./unit/"\" -O2 -pipe -march=native -fPIE -Wl,-O1 -Wl,--as-needed -pie -o unit/test-pbkdf2 unit/test-pbkdf2.o ell/libell-private.la libtool: link: x86_64-pc-linux-gnu-gcc -fvisibility=hidden -DUNITDIR=\"/var/tmp/portage/dev-libs/ell-0.5/work/ell-0.5/unit/\" -DCERTDIR=\"./unit/\" -O2 -pipe -march=native -fPIE -Wl,-O1 -Wl,--as-needed -pie -o unit/test-pbkdf2 unit/test-pbkdf2.o ell/.libs/libell-private.a ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-hardened_test_20180512-194415 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python3.6 (fallback) [3] python2.7 (fallback) [4] pypy3 (fallback) [5] pypy (fallback) java-config: The following VMs are available for generation-2: emerge -qpv dev-libs/ell [ebuild N ] dev-libs/ell-0.5 USE="(pie) -glib" ABI_X86="(64) -32 (-x32)"
Created attachment 534820 [details] emerge-info.txt
Created attachment 534822 [details] dev-libs:ell-0.5:20180604-111137.log
Created attachment 534824 [details] emerge-history.txt
Created attachment 534826 [details] environment
Created attachment 534828 [details] etc.portage.tbz2
Created attachment 534830 [details] logs.tbz2
Created attachment 534832 [details] temp.tbz2
Created attachment 549170 [details] build.log for version 0.9 I'm also seeing this, on version 0.9. I didn't have any earlier versions installed, so I suspect I would see it on them, too.
I think the failure is due to some kernel functionality missing. More precisely, ell needs the following kernel config options: CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_CRYPTO_USER_API=y CONFIG_CRYPTO_USER_API_HASH=y CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_SHA1=y CONFIG_KEY_DH_OPERATIONS=y (see README of ell). The failure of the test-uuid (or more precisely the lack of UUID capability in ell) is due to ell using the md5 capability of the kernel via the user crypto API (see create_alg() in ell/checksum.c called by l_checksum_new() called by the UUID functions). I'll guess the ebuild should check for those kernel options when getting merged because library users might expect that ell has the capability of generating UUIDs (which it cannot without those kernel options).
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e5908a30fa022635daf42c7d0226965ff6da3045 commit e5908a30fa022635daf42c7d0226965ff6da3045 Author: Ben Kohler <bkohler@gentoo.org> AuthorDate: 2020-03-25 15:33:26 +0000 Commit: Ben Kohler <bkohler@gentoo.org> CommitDate: 2020-03-25 15:37:40 +0000 dev-libs/ell: bump to 0.30 & add CONFIG_* checks Closes: https://bugs.gentoo.org/714716 Closes: https://bugs.gentoo.org/657352 Package-Manager: Portage-2.3.95, Repoman-2.3.21 Signed-off-by: Ben Kohler <bkohler@gentoo.org> dev-libs/ell/Manifest | 1 + dev-libs/ell/ell-0.30.ebuild | 59 ++++++++++++++++++++++++++++++++++++++++++++ dev-libs/ell/ell-9999.ebuild | 15 ++++++++++- 3 files changed, 74 insertions(+), 1 deletion(-)
