1 |
On Montag 06 Juli 2009, Jarry wrote: |
2 |
> Hi, |
3 |
> I just tried to update gcc (actually, it is just recompiling with |
4 |
> new nptl flag), but it failed with this messages: |
5 |
> __________ |
6 |
> |
7 |
> >>> Failed to emerge sys-devel/gcc-4.3.2-r3, Log file: |
8 |
> >>> |
9 |
> >>> '/var/tmp/portage/sys-devel/gcc-4.3.2-r3/temp/build.log' |
10 |
> |
11 |
> * Messages for package sys-devel/gcc-4.3.2-r3: |
12 |
> |
13 |
> * |
14 |
> * ERROR: sys-devel/gcc-4.3.2-r3 failed. |
15 |
> * Call stack: |
16 |
> * ebuild.sh, line 49: Called src_compile |
17 |
> * environment, line 4870: Called toolchain_src_compile |
18 |
> * environment, line 5396: Called gcc_src_compile |
19 |
> * environment, line 3094: Called gcc_do_make |
20 |
> * environment, line 2884: Called die |
21 |
> * The specific snippet of code: |
22 |
> * emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" |
23 |
> LIBPATH="${ |
24 |
> LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" |
25 |
> ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}"; |
26 |
> * The die message: |
27 |
> * emake failed with bootstrap-lean |
28 |
> * |
29 |
> * If you need support, post the topmost build error, and the call |
30 |
> stack if relevant. |
31 |
> * A complete build log is located at |
32 |
> '/var/tmp/portage/sys-devel/gcc-4.3.2-r3/temp/build.log'. |
33 |
> * The ebuild environment file is located at |
34 |
> '/var/tmp/portage/sys-devel/gcc-4.3.2-r3/temp/environment'. |
35 |
> __________ |
36 |
> |
37 |
> What does it mean, and how can I fix it??? |
38 |
> |
39 |
> Jarry |
40 |
|
41 |
that means that you forgot to copy the important part. You just copied the |
42 |
pretty useless vanilla portage error. Not the real error some lines above that |
43 |
one. |