| 1 |
Jules Colding schreef: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> "emerge --sync && emerge -vauDN" today gave me the following error. |
| 5 |
> |
| 6 |
|
| 7 |
> adding: skin/modern/communicator/cookie/taskbar-cookie.gif (stored 0%) |
| 8 |
> adding: skin/modern/communicator/cookie/status-cookie.gif (stored 0%) |
| 9 |
> +++ making chrome /var/tmp/portage/homedir => ../../dist/bin/chrome/classic.jar |
| 10 |
> error: file './resources/skin/classic/taskbar-cookie.gif' doesn't exist at ../../config/make-jars.pl line 418. |
| 11 |
> gmake[3]: *** [libs] Error 2 |
| 12 |
> gmake[3]: Leaving directory `/var/tmp/portage/mozilla-firefox-1.0.6-r2/work/mozilla/extensions/cookie' |
| 13 |
> gmake[2]: *** [libs] Error 2 |
| 14 |
> gmake[2]: Leaving directory `/var/tmp/portage/mozilla-firefox-1.0.6-r2/work/mozilla/extensions' |
| 15 |
> gmake[1]: *** [tier_94] Error 2 |
| 16 |
> gmake[1]: Leaving directory `/var/tmp/portage/mozilla-firefox-1.0.6-r2/work/mozilla' |
| 17 |
> make: *** [default] Error 2 |
| 18 |
> |
| 19 |
> !!! ERROR: www-client/mozilla-firefox-1.0.6-r2 failed. |
| 20 |
> !!! Function src_compile, Line 159, Exitcode 2 |
| 21 |
> !!! (no error message) |
| 22 |
> !!! If you need support, post the topmost build error, NOT this status message. |
| 23 |
> |
| 24 |
> ############## emerge --info ################# |
| 25 |
> omc-2 ~ # emerge --info |
| 26 |
> Portage 2.0.51.22-r2 (default-linux/amd64/2005.0, gcc-3.4.3, glibc-2.3.5-r0, 2.6.12-gentoo-r6 x86_64) |
| 27 |
> ================================================================= |
| 28 |
> System uname: 2.6.12-gentoo-r6 x86_64 AMD Opteron(tm) Processor 252 |
| 29 |
> Gentoo Base System version 1.6.13 |
| 30 |
> dev-lang/python: 2.3.5 |
| 31 |
> sys-apps/sandbox: 1.2.11 |
| 32 |
> sys-devel/autoconf: 2.13, 2.59-r6 |
| 33 |
> sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 |
| 34 |
> sys-devel/binutils: 2.15.92.0.2-r10 |
| 35 |
> sys-devel/libtool: 1.5.18-r1 |
| 36 |
> virtual/os-headers: 2.6.11-r2 |
| 37 |
> ACCEPT_KEYWORDS="amd64" |
| 38 |
> AUTOCLEAN="yes" |
| 39 |
> CBUILD="x86_64-pc-linux-gnu" |
| 40 |
> CFLAGS="-march=k8 -O2 -pipe" |
| 41 |
> CHOST="x86_64-pc-linux-gnu" |
| 42 |
> CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" |
| 43 |
> CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" |
| 44 |
> CXXFLAGS="-march=k8 -O2 -pipe" |
| 45 |
|
| 46 |
Well, since I just (literally, 10 minutes ago) emerged |
| 47 |
mozilla-firefox-1.0.6-r2, and had no problems on a 32-bit system, I must |
| 48 |
suspect that this is a 64-bit issue. |
| 49 |
|
| 50 |
In that regard, I see at least one thing in your emerge info that has |
| 51 |
been called into question for 64-bit users in recent threads: |
| 52 |
|
| 53 |
CFLAGS="-march=k8 |
| 54 |
|
| 55 |
I am, of course, not a 64-bit user, so I don't know anything about this, |
| 56 |
but I have seen several responses to similar questions that suggest that |
| 57 |
the correct flag is |
| 58 |
|
| 59 |
march=amd64 |
| 60 |
|
| 61 |
Oh, and despite what Patrick said, I think you were right to post here |
| 62 |
first-- no need to clog up b.g.o with what might be a configuration |
| 63 |
problem and waste developer's time closing an invalid bug. |
| 64 |
|
| 65 |
I think it's always wise to try to make sure that it really is a bug |
| 66 |
before posting it. |
| 67 |
|
| 68 |
And it seems to me that if there is a bug, it might be a *documentation* |
| 69 |
bug (because the other person who mentioned using march=k8 said that |
| 70 |
that was the recommendation of the docs, but that seems to no longer be |
| 71 |
the case, if people using this flag are regularly receiving compilation |
| 72 |
errors). |
| 73 |
|
| 74 |
Holly |
| 75 |
-- |
| 76 |
gentoo-user@g.o mailing list |
Archives