I'm not sure if the Gnome team is responsible for this, or someone else needs to take a look, so please re-assign if I've gotten this wrong :) Trying to emerge nautilus-2.24.2 fails with the following : /usr/lib/gcc/i686-pc-linux-gnu/4.3.2/../../../../i686-pc-linux-gnu/bin/ld:.libs/nautilus-file-info.o: file format not recognized; treating as linker script /usr/lib/gcc/i686-pc-linux-gnu/4.3.2/../../../../i686-pc-linux-gnu/bin/ld:.libs/nautilus-file-info.o:1: syntax error collect2: ld returned 1 exit status make[2]: *** [libnautilus-extension.la] Error 1 make[2]: Leaving directory `/var/tmp/portage/gnome-base/nautilus-2.24.2/work/nautilus-2.24.2/libnautilus-extension' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gnome-base/nautilus-2.24.2/work/nautilus-2.24.2' make: *** [all] Error 2 * * ERROR: gnome-base/nautilus-2.24.2 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2588: Called gnome2_src_compile * environment, line 1972: 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/nautilus-2.24.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/gnome-base/nautilus-2.24.2/temp/environment'. * emerge --info : trinity ~ # emerge --info Portage 2.1.6_rc3 (default/linux/x86/2008.0/desktop, gcc-4.3.2, glibc-2.8_p20080602-r0, 2.6.27.6 i686) ================================================================= System uname: Linux-2.6.27.6-i686-Intel-R-_Core-TM-2_Duo_CPU_P8400_@_2.26GHz-with-glibc2.0 Timestamp of tree: Fri, 05 Dec 2008 19:18:01 +0000 ccache version 2.4 [enabled] app-shells/bash: 3.2_p48 dev-java/java-config: 1.3.7-r1, 2.1.6-r1 dev-lang/python: 2.4.4-r13, 2.5.2-r8 dev-util/ccache: 2.4-r8 dev-util/cmake: 2.6.2 sys-apps/baselayout: 2.0.0 sys-apps/openrc: 0.3.0-r1 sys-apps/sandbox: 1.2.18.1-r3 sys-devel/autoconf: 2.13, 2.63 sys-devel/automake: 1.5, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.19 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 2.2.6a virtual/os-headers: 2.6.27-r2 ACCEPT_KEYWORDS="x86 ~x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=prescott -O3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-march=prescott -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="ccache collision-protect cvs distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="en_GB.UTF-8" LDFLAGS="-Wl,-O1" LINGUAS="en en_GB" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync1.sg.gentoo.org/gentoo-portage" USE="3dnow X a52 aac aalib acl acpi adns alsa apache2 avahi bash-completion berkdb bluetooth branding bzip2 cairo cddb cdr cgi cli cracklib crypt cscope css ctype cups curl cvs dbus directfb dri dts dv dvd dvdr dvdread emboss encode exif expat fam fbcon ffmpeg firefox flac fltk fontconfig fortran ftp gd gdbm geoip gif gimp gnome gnutls gphoto2 gpm gps gstreamer gtk gtkhtml hal hddtemp iconv ieee1394 imagemagick innodb ipod ipv6 isdnlog jabber java java6 jingle jpeg lame libnotify lm_sensors mad mailwrapper matroska memlimit midi mikmod mime mmap mmx mp3 mpeg mplayer msn mudflap musicbrainz mysql nautilus ncurses networkmanager nls nptl nptlonly nsplugin offensive ogg opengl openmp pam pcre pda pdf perl php png posix ppds pppd python qt3support quicktime raw rdesktop readline recode reflection rss ruby samba sdl session simplexml smp snmp sockets spell spl sse sse2 ssl startup-notification subversion svg svga sysfs syslog tcpd threads tidy tiff timidity truetype unicode usb vcd vim-syntax vnc vorbis wifi win32codecs wmf x264 x86 xattr xcb xcomposite xinetd xml xorg xosd xpm xsl xulrunner xv xvid yahoo zeroconf zlib" ALSA_CARDS="hda-intel" 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" ELIBC="glibc" INPUT_DEVICES="keyboard mouse synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en en_GB" USERLAND="GNU" VIDEO_CARDS="intel vga vesa vmware" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY Attaching build.log FWIW as well. The same version builds just fine with gcc-4.1.2
Created attachment 174352 [details] nautilus-2.24.2 build.log Here's the build.log
@toolchain, what say you? This is really weird bug, one I've never seen before... Thanks
So after going through a number of things with dang on IRC, If my CFLAGS have a -O2 then it builds fine with gcc-4.3.2, with -O3 it fails.
Re-assigning to toolchain, as upstream gnome doesn't support O3. Quite possibly, toolchain is interested in fixing this.
build it again with FEATURES=-ccache and -O3 in CFLAGS. that error is not indicative of a failure in gcc.
(In reply to comment #5) > build it again with FEATURES=-ccache and -O3 in CFLAGS. that error is not > indicative of a failure in gcc. Okay, it builds fine with ccache disabled and 03.
might be related to Bug 196243 ... what needs to go down now is you find the offending ccache object (dont delete it!) and the offending cpp output that ccache is producing but detecting as the old rather than the new ...
(In reply to comment #7) > might be related to Bug 196243 ... what needs to go down now is you find the > offending ccache object (dont delete it!) and the offending cpp output that > ccache is producing but detecting as the old rather than the new ... And pray how Mr.SpanKY do I go about doing all this? :D
And FWIW, mine is a 32 bit system...
in which case, that implies you have cache corruption ... usually this occurs due to fdisk troubles/whatever on files in the ccache dir building lots of stuff -> locks up system -> corrupts ccache -> screws future builds to start with, retrigger the build failure and then find the md5sum of the failing file (.libs/nautilus-file-info.o). make sure that isnt a 0 byte file, and then find the file in your ccache dir that matches.
(In reply to comment #10) > to start with, retrigger the build failure and then find the md5sum of the > failing file (.libs/nautilus-file-info.o). make sure that isnt a 0 byte file, > and then find the file in your ccache dir that matches. I can re-trigger the failure, got the md5sum too, but that file isn't in the cache. No matching filename for that md5sum. Suggestions? The difference it, before (the last time I looked) nautilus-file-info.o was a file with some hex data etc, and running file would show just "data". Now, the file is a clump of code and file says ASCII C Program Text. Does that give you any pointers? I could attach nautilus-file-info.o if needed.
i dont suppose you feel like running a full fdisk on the disk ? the info i need is the colliding the file and the input ccache uses to get to the colliding file ... but first do the fdisk ...
(In reply to comment #12) > i dont suppose you feel like running a full fdisk on the disk ? fdisk? as in fdisk -l? or fsck? > the info i need is the colliding the file and the input ccache uses to get to > the colliding file ... but first do the fdisk ... Sure, as soon as you clarify :)
sorry, i was working on another bug where the guy has fdisk problems i of course mean fsck ...
(In reply to comment #14) > sorry, i was working on another bug where the guy has fdisk problems Tut Tut! > i of course mean fsck ... Alright. This happens in a few hours..since it's 0400 now. I'll let you know how it goes.
(In reply to comment #15) > Alright. This happens in a few hours..since it's 0400 now. I'll let you know > how it goes. So sorry. I'd done this ages ago...and never replied. ########### reiserfsck --check started at Wed Dec 10 23:47:01 2008 ########### Replaying journal.. Reiserfs journal '/dev/sda6' in blocks [18..8211]: 0 transactions replayed Checking internal tree..finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 258778 Internal nodes 1692 Directories 154990 Other files 1155945 Data block pointers 11575021 (97 of them are zero) Safe links 0 ########### reiserfsck finished at Thu Dec 11 00:11:40 2008 ########### ########### reiserfsck --check started at Thu Dec 11 00:14:28 2008 ########### Replaying journal.. Reiserfs journal '/dev/sda7' in blocks [18..8211]: 0 transactions replayed Checking internal tree..finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 39635 Internal nodes 268 Directories 77983 Other files 167520 Data block pointers 10749396 (35 of them are zero) Safe links 0 ########### reiserfsck finished at Thu Dec 11 00:17:04 2008 ########### That's both / and /home. It's a new comp/new install so I really didn't expect to see any issues with fsck
and if you clear your ccache, does it work ?
Is this still a problem you can reproduce?
