On Sun, 2005-07-24 at 14:22 +0200, Jules Colding wrote: > On Sat, 2005-07-23 at 11:51 -0700, Zac Medico wrote: > > Jules Colding wrote: > > > Hi, > > > > > > "emerge --sync && emerge -vauDN" today gave me the following error. > > > > > [snip] > > > adding: content/cookie/contents.rdf (stored 0%) > > > +++ making > > chrome > > /var/tmp/portage/mozilla-firefox-1.0.6-r2/work/mozilla/extensions/cookie > > => ../../dist/bin/chrome/modern.jar > > > zip warning: ../modern.jar not found or empty > > > adding: skin/modern/communicator/cookie/taskbar-cookie.gif (stored > > 0%) > > > adding: skin/modern/communicator/cookie/status-cookie.gif (stored > > 0%) > > > +++ making chrome /var/tmp/portage/homedir > > => ../../dist/bin/chrome/classic.jar > > > error: file './resources/skin/classic/taskbar-cookie.gif' doesn't > > exist at ../../config/make-jars.pl line 418. > > > > This seems like a continuation of the previous build problems that you > > have had with firefox (where we were discussing MAKEOPTS). > > Yes, that is my thought too. > > > Assuming that others cannot reproduce this (sorry, I don't have my > > amd64 right now), there's still something wrong with your build system > > somewhere. > > I think that I am the only one that can show the problem so you might > very well be correct. > > > This could be a shot in the dark, but I think that you should remerge > > your autoconf and automake packages to see if that affects this. > > I'll be doing that.
OK, I get a segfault doing that: ############## snip ############### test -z "/usr/share/automake-1.9/Automake" || mkdir -p -- "/var/tmp/portage/automake-1.9.5/image//usr/share/automake-1.9/Automake" /bin/install -c -m 644 'Config.pm' '/var/tmp/portage/automake-1.9.5/image//usr/share/automake-1.9/Automake/Config.pm' make[4]: Leaving directory `/var/tmp/portage/automake-1.9.5/work/automake-1.9.5/lib/Automake' make[3]: Leaving directory `/var/tmp/portage/automake-1.9.5/work/automake-1.9.5/lib/Automake' make[2]: Leaving directory `/var/tmp/portage/automake-1.9.5/work/automake-1.9.5/lib/Automake' Making install in am make[2]: Entering directory `/var/tmp/portage/automake-1.9.5/work/automake-1.9.5/lib/am' make[3]: Entering directory `/var/tmp/portage/automake-1.9.5/work/automake-1.9.5/lib/am' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/share/automake-1.9/am" || mkdir -p -- "/var/tmp/portage/automake-1.9.5/image//usr/share/automake-1.9/am" /bin/sh: line 1: 16093 Segmentation fault mkdir -p -- "/var/tmp/portage/automake-1.9.5/image//usr/share/automake-1.9/am" make[3]: *** [install-dist_amDATA] Error 139 make[3]: Leaving directory `/var/tmp/portage/automake-1.9.5/work/automake-1.9.5/lib/am' make[2]: *** [install-am] Error 2 make[2]: Leaving directory `/var/tmp/portage/automake-1.9.5/work/automake-1.9.5/lib/am' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/automake-1.9.5/work/automake-1.9.5/lib' make: *** [install-recursive] Error 1 !!! ERROR: sys-devel/automake-1.9.5 failed. !!! Function src_install, Line 36, Exitcode 2 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message. ############## snip ############### Wouldn't it be a good idea on this point to reemerge coreutils or maybe the whole of "system"? Is the correct way doing: emerge -e system emerge -e system emerge -e world emerge -e world ? or is a single "emerge -e system" sufficient? Thanks, jules -- gentoo-user@gentoo.org mailing list
