libtool: link: x86_64-pc-linux-gnu-gcc -I../../doc/sdk/include/rsaref220 -I../../plugins_tools/util -O2 -pipe -march=native -pthread -I/usr/include/PCSC -o .libs/threads threads.o ../../cardcomm/pkcs11/src/.libs/libbeidpkcs11.so -lpthread ./.libs/libtestlib.a /usr/lib64/libpcsclite.so -ldl -lrt -pthread x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -pthread -I/usr/include/PCSC -I../../doc/sdk/include/rsaref220 -I../../plugins_tools/util -O2 -pipe -march=native -c -o sign-sign.o `test -f 'sign.c' || echo './'`sign.c sign.c:41:12: error: static declaration of ‘RSA_set0_key’ follows non-static declaration 41 | static int RSA_set0_key(RSA *r, BIGNUM *n, BIGNUM *e, BIGNUM *d) { | ^~~~~~~~~~~~ In file included from sign.c:37: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop-libressl_test-20190726-201531 ------------------------------------------------------------------- Please see the tracker bug for details. gcc-config -l: [1] x86_64-pc-linux-gnu-9.1.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Rust versions: [1] rust-1.36.0 * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.12.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpvO app-crypt/eid-mw [ebuild N ] app-crypt/eid-mw-4.4.11 USE="dialogs gtk p11v220 -p11-kit"
Created attachment 585564 [details] emerge-info.txt
Created attachment 585566 [details] app-crypt:eid-mw-4.4.11:20190802-074516.log
Created attachment 585568 [details] emerge-history.txt
Created attachment 585570 [details] environment
Created attachment 585572 [details] etc.portage.tbz2
Created attachment 585574 [details] logs.tbz2
Created attachment 585576 [details] temp.tbz2
Created attachment 585578 [details] tests.tbz2
Created attachment 585746 [details, diff] Fix test sign.c Hi Toralf, I assume this bug does not occur with the live ebuild : sign.c has been reworked in the upcoming pre 5 release and the bug seems fixed. Patch in attachment is a backport of the new sign.c. Can you apply this patch before ebuild compile and tell me if it fixes the bug for you.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5724b3d83e696251df1fee776afdf55226f85cd9 commit 5724b3d83e696251df1fee776afdf55226f85cd9 Author: Amy Liffey <amynka@gentoo.org> AuthorDate: 2019-08-15 19:18:00 +0000 Commit: Amy Liffey <amynka@gentoo.org> CommitDate: 2019-08-15 19:19:35 +0000 app-crypt/eid-mw: remove old 4.4.11 Closes: https://bugs.gentoo.org/691308 Suggested-by: Vincent Hardy <vincent.hardy.be@gmail.com> Package-Manager: Portage-2.3.69, Repoman-2.3.16 Signed-off-by: Amy Liffey <amynka@gentoo.org> app-crypt/eid-mw/Manifest | 1 - app-crypt/eid-mw/eid-mw-4.4.11.ebuild | 93 ----------------------------------- 2 files changed, 94 deletions(-)
