Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 326775 - app-crypt/seahorse-2.26.2 fails to build due to a colon in a path
Summary: app-crypt/seahorse-2.26.2 fails to build due to a colon in a path
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
Depends on:
Reported: 2010-07-03 21:58 UTC by Richard Kaiser
Modified: 2010-07-12 12:33 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

seahorse-2.30.1 build log (build.log,296.85 KB, text/plain)
2010-07-05 00:32 UTC, Richard Kaiser

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Kaiser 2010-07-03 21:58:16 UTC
revdep-rebuild wants to rebuild this application on my system, but the build fails. The error message is unknown file type, but two different paths seem to be concatenated together with a colon. 

From the log:

/usr/lib/gcc/x86_64-pc-linux-gnu/4.4.3/../../../../x86_64-pc-linux-gnu/bin/ld:/usr/lib64/ file format not recognized; treating as linker script

The ":" between bin/ld and /usr/lib64 looks breaks this as a path.

I looked through the makefiles in the build directory, but I did not see anything wrong. There are a lot of files and I wasn't really sure what to look for.

Bugzilla and and the forums did not provide any clues.

Reproducible: Always

Steps to Reproduce:
1. revdep-rebuild (on my system) or emerge -a --oneshot =app-crypt/seahorse-2.26.2

This problem may be triggered by something unique in my system.
Actual Results:  
From emerge:

>>> Failed to emerge app-crypt/seahorse-2.26.2, Log file:

>>>  '/var/tmp/portage/app-crypt/seahorse-2.26.2/temp/build.log'

 * Messages for package app-crypt/seahorse-2.26.2:

 * ERROR: app-crypt/seahorse-2.26.2 failed:
 *   compile failure
 * Call stack:
 *, line   54:  Called src_compile
 *   environment, line 3012:  Called gnome2_src_compile
 *   environment, line 2341:  Called die
 * The specific snippet of code:
 *       emake || die "compile failure"
 * If you need support, post the output of 'emerge --info =app-crypt/seahorse-2.26.2',
 * the complete build log and the output of 'emerge -pqv =app-crypt/seahorse-2.26.2'.
 * The complete build log is located at '/var/tmp/portage/app-crypt/seahorse-2.26.2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-crypt/seahorse-2.26.2/temp/environment'.
 * S: '/var/tmp/portage/app-crypt/seahorse-2.26.2/work/seahorse-2.26.2'
 * revdep-rebuild failed to emerge all packages.
 * you have the following choices:

End of seahorse build log
bin/sh ../libtool --tag=CC   --mode=link x86_64-pc-linux-gnu-gcc  -march=k8 -O2 -pipe -fno-delete-null-pointer-checks  -Wl,-O1 -o seahorse-ssh-askpass seahorse-ssh-askpass.o ../libseahorse/ ../libcryptui/ -pthread -lglade-2.0 -lxml2 -lgconf-2 -lgthread-2.0 -lrt -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0   -L/usr/lib64 -lgpgme -lassuan -L/usr/lib64 -lgpg-error -L/usr/lib64 -lgpg-error  -lsoup-2.4 -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0   -lgnome-keyring -lglib-2.0   -lavahi-common -lavahi-client -lavahi-glib -lglib-2.0   -ldbus-glib-1 -ldbus-1 -lpthread -lrt -lgobject-2.0 -lglib-2.0   -lgcr -lgtk-x11-2.0 -ltasn1 -lgp11 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0   
libtool: link: x86_64-pc-linux-gnu-gcc -march=k8 -O2 -pipe -fno-delete-null-pointer-checks -Wl,-O1 -o .libs/seahorse-ssh-askpass seahorse-ssh-askpass.o -pthread  ../libseahorse/.libs/libseahorse.a /var/tmp/portage/app-crypt/seahorse-2.26.2/work/seahorse-2.26.2/libcryptui/.libs/ -L/usr/lib64 ../libcryptui/.libs/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ -lpthread -lrt /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ -lresolv /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ /usr/lib64/ -lm /usr/lib64/ /usr/lib64/ -lz /usr/lib64/ /usr/lib64/ /usr/lib64/ -ldl /usr/lib64/ -pthread
/usr/lib/gcc/x86_64-pc-linux-gnu/4.4.3/../../../../x86_64-pc-linux-gnu/bin/ld:/usr/lib64/ file format not recognized; treating as linker script
/usr/lib/gcc/x86_64-pc-linux-gnu/4.4.3/../../../../x86_64-pc-linux-gnu/bin/ld:/usr/lib64/ syntax error
collect2: ld returned 1 exit status
make[2]: *** [seahorse-ssh-askpass] Error 1
make[2]: Leaving directory `/var/tmp/portage/app-crypt/seahorse-2.26.2/work/seahorse-2.26.2/ssh'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/app-crypt/seahorse-2.26.2/work/seahorse-2.26.2'
make: *** [all] Error 2

Expected Results:  
app-crypt/seahorse-2.26.2 successfully installed

I have held my system back to from upgrading to gnome 2.28.0. I didn't see any later unmasked version of seahorse so I don't think this is the direct cause of the problem.

#emerge --info =app-crypt/seahorse-2.26.2

Portage (default/linux/amd64/10.0, gcc-4.4.3, glibc-2.11.2-r0, 2.6.31-gentoo-r6 x86_64)
                        System Settings
System uname: Linux-2.6.31-gentoo-r6-x86_64-AMD_Athlon-tm-_64_Processor_3400+-with-gentoo-1.12.13
Timestamp of tree: Sat, 03 Jul 2010 02:00:01 +0000
app-shells/bash:     4.0_p37
dev-java/java-config: 2.1.11
dev-lang/python:     2.6.5-r2, 3.1.2-r3
dev-util/cmake:      2.6.4-r3
sys-apps/baselayout: 1.12.13
sys-apps/sandbox:    1.6-r2
sys-devel/autoconf:  2.13, 2.65
sys-devel/automake:  1.9.6-r3, 1.10.3, 1.11.1
sys-devel/binutils:  2.20.1-r1
sys-devel/gcc:       4.3.4, 4.4.3-r2
sys-devel/gcc-config: 1.4.1
sys-devel/libtool:   2.2.6b
virtual/os-headers:  2.6.30-r1
ACCEPT_LICENSE="* -@EULA dlj-1.1 googleearth AdobeFlash-10.1"
CFLAGS="-march=k8 -O2 -pipe -fno-delete-null-pointer-checks"
CONFIG_PROTECT="/etc /usr/share/X11/xkb /usr/share/config /var/lib/hsqldb"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-march=k8 -O2 -pipe -fno-delete-null-pointer-checks"
FEATURES="assume-digests distlocks fixpackages news parallel-fetch protect-owned sandbox sfperms strict unmerge-logs unmerge-orphans userfetch"
LINGUAS="en en_US"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
USE="X a52 aac acl alsa amd64 audiofile automount avahi bzip2 cairo cdparanoia cdr cli consolekit cracklib crypt css cups curl curlwrappers cxx dbus device-mapper dga dri dv dvd dvdr dvdread encode exif extras ffmpeg flac fortran fts3 gdbm gdu gif gnome gpm gstreamer gtk hal iconv ipv4 jadetex java java-nsplugin jpeg jpeg2k laptop lkdnssd mad mdnsresponder-compat midi mmx mng modules mp3 mpeg mudflap multilib musepack musicbrainz ncurses nls nptl nptlonly nsplugin ntplonly objc ogg openexr openmp osgapps oss pam pcre pdf perl png policykit ppds pppd python qt3support readline reflection scanner sdl session sndfile speex spell spl sqlite sse sse2 ssl svg sysfs theora tiff truetype unicode utils v4l v4l2 vcd vorbis wavpack wma wmf wmp x264 xen xorg xulrunner xvid xvmc zlib" ALSA_CARDS="intel8x0" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CAMERAS="canon casio" ELIBC="glibc" INPUT_DEVICES="evdev keyboard mouse synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en en_US" RUBY_TARGETS="ruby18" USERLAND="GNU" VIDEO_CARDS="nv nvidia" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" 
Comment 1 Pacho Ramos gentoo-dev 2010-07-04 16:36:19 UTC
Please install 2.28.1 or 2.30.1
Comment 2 Richard Kaiser 2010-07-04 21:38:39 UTC
Both app-crypt/seahorse-2.28.1 and -2.30.1 have the same problem.

Comment 3 Pacho Ramos gentoo-dev 2010-07-04 21:56:38 UTC
I am unable to reproduce, what app-crypt/gpgme are you running? Please attach build.log also
Comment 4 Richard Kaiser 2010-07-05 00:32:08 UTC
Created attachment 237511 [details]
seahorse-2.30.1 build log
Comment 5 Richard Kaiser 2010-07-05 05:57:31 UTC
*  app-crypt/gpgme
      Latest version available: 1.3.0
      Latest version installed: 1.3.0
Comment 6 Richard Kaiser 2010-07-05 06:34:02 UTC
Thanks for the hint, I downgraded pgpme to 1.2.0 and seahorse-2.30.1 installed.

[ebuild   R   ] app-crypt/gpgme-1.2.0 
[ebuild   R   ] app-crypt/seahorse-2.30.1 

This bug can be closed with this workaround available, or I will continue running tests until the root cause if found. I don't use PGP/GPG so this code is not a priority for me, but if this may effect other users then it probably should be fixed.
Comment 7 Pacho Ramos gentoo-dev 2010-07-05 09:42:30 UTC
It should work with 1.3.0 too (and works on my system), also, the error:
file format not recognized; treating as linker script

looks a bit like a "corruption" 

Do you have a fully updated system? Reading your first comment seems that you have some outdated packages coexisting with updated ones, and it's not a good idea, please update your system properly
Comment 8 Richard Kaiser 2010-07-12 12:33:53 UTC
My system is now fully updated without any sign of the problem. (Actually, my system was updated twice, once in my stable system and once in a backup/testing copy.) To me this looks like some type of incompatibility between old and new packages. There may still be a real problem, but if its not effecting anyone else then it is not worth hunting down to fix.