checking for dgettext in -lintl... no checking for LIBTASN1... no configure: error: libtasn1 not found. Building without it results in significant loss of functionality. To proceed use --without-libtasn1 !!! Please attach the following file when seeking support: !!! /var/tmp/portage/app-crypt/p11-kit-0.23.2/work/p11-kit-0.23.2-abi_x86_32.x86/config.log === This is an issue at stable === ------------------------------------------------------------------- This is an stable amd64 chroot image at a tinderbox (==build bot) name: 13.0-desktop_stable-abi32+64_20170902-123437 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * emerge -qpv app-crypt/p11-kit [ebuild N ] app-crypt/p11-kit-0.23.2 USE="asn1 libffi trust -debug" ABI_X86="32 (64) (-x32)"
Created attachment 491996 [details] emerge-info.txt
Created attachment 491998 [details] app-crypt:p11-kit-0.23.2:20170903-014400.log
Created attachment 492000 [details] emerge-history.txt
Created attachment 492002 [details] environment
Created attachment 492004 [details] etc.portage.tbz2
Created attachment 492006 [details] logs.tbz2
Created attachment 492008 [details] temp.tbz2
You have something wrong with your pkg-config settings. --- configure:16917: checking for LIBTASN1 configure:16924: $PKG_CONFIG --exists --print-errors "libtasn1 >= 2.3" Package libtasn1 was not found in the pkg-config search path. Perhaps you should add the directory containing `libtasn1.pc' to the PKG_CONFIG_PATH environment variable No package 'libtasn1' found configure:16927: $? = 1 configure:16941: $PKG_CONFIG --exists --print-errors "libtasn1 >= 2.3" Package libtasn1 was not found in the pkg-config search path. Perhaps you should add the directory containing `libtasn1.pc' to the PKG_CONFIG_PATH environment variable No package 'libtasn1' found --- Same issue as bug#629704, please try to find root cause.
(In reply to Alon Bar-Lev from comment #8) yep, and I feal those issues mostly do occur for ABI_X86="32 64"
*** This bug has been marked as a duplicate of bug 629704 ***
