On Sat, 2005-07-23 at 23:26 +0200, Richard Fish wrote: > Hmm, since others with similar systems cannot duplicate the problem, I > decided to capture all of the build output on my system (P4) and > compare. Jules, there is definitely something not right on your system, > but I don't know what yet. You get the following: > > +++ overriding content/cookie/contents.rdf > 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. > > The "/var/tmp/portage/homedir" is wrong.
Sharp eyes. I didn't notice that one. > On my system, I get: > > +++ overriding content/cookie/contents.rdf > 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/mozilla-firefox-1.0.6-r2/work/mozilla/extensions/cookie => > ../../dist/bin/chrome/classic.jar > > Using the wrong version of autoconf/automake is the only thing I can think of > that would cause this kind of thing. > > What do you get if you do: > > # which autoconf omc-2 ~ # which autoconf /usr/bin/autoconf > # autoconf --version omc-2 ~ # autoconf --version autoconf (GNU Autoconf) 2.59 Written by David J. MacKenzie and Akim Demaille. I am trying to reemerge autoconf and automake as zac advised. BTW, the "homedir" above is now empty, but is does still exists. It has other permissions that the other directories. Like: ########### snip ########## drwxr-xr-x 3 portage portage 72 Jul 21 03:05 grep-2.5.1-r6 drwxr-xr-x 3 portage portage 72 Jul 21 02:10 gzip-1.3.5-r5 drwxrws--- 4 portage portage 120 Jul 22 20:58 homedir drwxr-xr-x 3 portage portage 72 Jul 19 21:41 linux-headers-2.6.8.1-r4 ########### snip ########## Don't know if that is significant, but is sure does look suspicious... Best regards, jules -- [email protected] mailing list
