From: Jules Colding <colding@omesc.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2
Date: Sun, 24 Jul 2005 14:38:10 +0200 [thread overview]
Message-ID: <1122208690.11897.14.camel@omc-2.omesc.com> (raw)
In-Reply-To: <1122207733.11897.2.camel@omc-2.omesc.com>
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
next prev parent reply other threads:[~2005-07-24 10:43 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 11:38 [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2 Jules Colding
2005-07-23 12:36 ` Patrick Börjesson
2005-07-23 12:50 ` Holly Bostick
2005-07-23 13:14 ` Jules Colding
2005-07-23 15:51 ` Patrick Börjesson
2005-07-23 16:37 ` Richard Fish
2005-07-23 17:08 ` Patrick Börjesson
2005-07-23 18:19 ` Richard Fish
2005-07-23 23:02 ` Patrick Börjesson
2005-07-24 12:43 ` Jules Colding
2005-07-25 2:09 ` Holly Bostick
2005-07-23 18:38 ` neil
2005-07-24 17:23 ` Neil Bothwick
2005-07-23 18:46 ` Bob Sanders
2005-07-23 18:51 ` Zac Medico
2005-07-23 21:26 ` Richard Fish
2005-07-24 12:28 ` Jules Colding
2005-07-24 11:07 ` Jules Colding
2005-07-24 13:20 ` Richard Fish
2005-07-24 13:28 ` Jules Colding
2005-07-24 13:51 ` Richard Fish
2005-07-24 13:57 ` Jules Colding
2005-07-24 13:58 ` Richard Fish
2005-07-24 14:27 ` Jules Colding
2005-07-24 14:43 ` Rumen Yotov
2005-07-24 14:47 ` Jules Colding
2005-07-24 15:06 ` [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2 (AMD64 users please help) Richard Fish
2005-07-24 15:12 ` Jules Colding
2005-07-24 18:10 ` Bob Sanders
2005-07-24 18:59 ` Jules Colding
2005-07-24 19:14 ` Richard Fish
2005-07-26 1:37 ` Bob Sanders
2005-07-24 14:00 ` [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2 Zac Medico
2005-07-24 15:29 ` neil
2005-07-24 12:22 ` Jules Colding
2005-07-24 12:38 ` Jules Colding [this message]
2005-07-24 12:48 ` Richard Fish
2005-07-24 13:10 ` Jules Colding
2005-07-24 13:30 ` Richard Fish
2005-07-24 13:28 ` Rumen Yotov
2005-07-24 13:35 ` Jules Colding
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1122208690.11897.14.camel@omc-2.omesc.com \
--to=colding@omesc.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox