Bug 270226 – gnome-base/gnome-keyring-2.26.1-r1 fails to compile

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Sergey Morozov 2009-05-17 18:13:11 UTC]

The part of the emerge output:

libtool: link: x86_64-pc-linux-gnu-gcc -Wall -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wsign-compare -O2 -pipe -mtune=core2 -march=core2 -mmmx -msse -msse2 -msse3 -mssse3 -mfpmath=sse -fomit-frame-pointer -mcx16 -msahf -Wno-strict-aliasing -Wno-sign-compare -Wl,-O1 -o .libs/gcr-scan .libs/gcr-scan.o -Wl,-O1  ../../../gcr/.libs/libgcr.so -L/usr/lib64 /var/tmp/portage/gnome-base/gnome-keyring-2.26.1-r1/work/gnome-keyring-2.26.1/gp11/.libs/libgp11.so /usr/lib64/libgthread-2.0.so -lrt /usr/lib64/libgcrypt.so /usr/lib64/libgpg-error.so /usr/lib64/libtasn1.so /usr/lib64/libgtk-x11-2.0.so /usr/lib64/libgdk-x11-2.0.so /usr/lib64/libatk-1.0.so /usr/lib64/libgdk_pixbuf-2.0.so /usr/lib64/libgio-2.0.so /usr/lib64/libpangocairo-1.0.so /usr/lib64/libpangoft2-1.0.so /usr/lib64/libcairo.so /usr/lib64/libpixman-1.so /usr/lib64/libdirectfb.so /usr/lib64/libfusion.so /usr/lib64/libdirect.so /usr/lib64/libglitz-glx.so /usr/lib64/libGL.so /usr/lib64/libXext.so -lpthread /usr/lib64/libglitz.so /usr/lib64/libpng12.so /usr/lib64/libxcb-render-util.so /usr/lib64/libxcb-render.so /usr/lib64/libXrender.so /usr/lib64/libX11.so /usr/lib64/libxcb-xlib.so /usr/lib64/libxcb.so /usr/lib64/libXau.so /usr/lib64/libXdmcp.so /usr/lib64/libpango-1.0.so -lm /usr/lib64/libfontconfig.so /usr/lib64/libfreetype.so -lz /usr/lib64/libexpat.so /usr/lib64/libgobject-2.0.so /usr/lib64/libgmodule-2.0.so -ldl /usr/lib64/libglib-2.0.so -pthread                                                  
gtk-doc: Running scanner gcr-scan                                                                                     
gcr-scan: gck-rpc-module.c:228: call_connect: Assertion `pkcs11_socket_path[0]' failed.                               
Scan failed:
make[4]: *** [scan-build.stamp] Error 255
make[4]: Leaving directory `/var/tmp/portage/gnome-base/gnome-keyring-2.26.1-r1/work/gnome-keyring-2.26.1/docs/reference/gcr'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/gnome-base/gnome-keyring-2.26.1-r1/work/gnome-keyring-2.26.1/docs/reference'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/gnome-base/gnome-keyring-2.26.1-r1/work/gnome-keyring-2.26.1/docs'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/gnome-base/gnome-keyring-2.26.1-r1/work/gnome-keyring-2.26.1'
make: *** [all] Error 2
 *
 * ERROR: gnome-base/gnome-keyring-2.26.1-r1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 1533:  Called gnome2_src_compile
 *             environment, line 1198:  Called die
 * The specific snippet of code:
 *       emake || die "compile failure"
 *  The die message:
 *   compile failure
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/gnome-base/gnome-keyring-2.26.1-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/gnome-base/gnome-keyring-2.26.1-r1/temp/environment'.
 *

>>> Failed to emerge gnome-base/gnome-keyring-2.26.1-r1, Log file:

>>>  '/var/tmp/portage/gnome-base/gnome-keyring-2.26.1-r1/temp/build.log'


Reproducible: Always

Steps to Reproduce:
emerge =gnome-base/gnome-keyring-2.26.1-r1

[Comment 1 Sergey Morozov 2009-05-17 18:14:18 UTC]

Created attachment 191575 [details]
Build log

[Comment 2 Sergey Morozov 2009-05-17 18:15:29 UTC]

Created attachment 191576 [details]
emerge --info

[Comment 3 Gilles Dartiguelongue (RETIRED) 2009-05-17 18:26:17 UTC]

*** This bug has been marked as a duplicate of bug 267957 ***